Thanks to visit codestin.com
Credit goes to github.com

Skip to content

upgrade from 5.2 to 5.3 steps #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jan 20, 2025
Merged

upgrade from 5.2 to 5.3 steps #85

merged 4 commits into from
Jan 20, 2025

Conversation

Jurj-Bogdan
Copy link
Member

Let me know of any changes. Also, should it be more in depth?

closes #84

@arhimede
Copy link
Member

@Jurj-Bogdan you need to edit another file to have that page added to menu
docs/book/v5/upgrading/UPGRADE-5.3.md

@bidi47
Copy link
Member

bidi47 commented Jan 17, 2025

@Jurj-Bogdan you need to edit another file to have that page added to menu docs/book/v5/upgrading/UPGRADE-5.3.md

it's this file that is used to place the links in the menu
https://github.com/dotkernel/api-documentation/blob/main/mkdocs.yml

@Jurj-Bogdan
Copy link
Member Author

@bidi47 @arhimede

Added a few phrases where applicable, and tweaked the mkdocs.yml file so the new pages are added to the menu.
Also moved the old upgrading.md under the new upgrading

mkdocs.yml Outdated
@@ -22,7 +22,9 @@ nav:
- "Doctrine ORM": v5/installation/doctrine-orm.md
- "Test the Installation": v5/installation/test-the-installation.md
- "FAQ": v5/installation/faq.md
- Upgrading: v5/upgrading.md
- Upgrading:
- "Upgrading": v5/upgrading/upgrading.md
Copy link
Member

@bidi47 bidi47 Jan 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change to "Upgrade procedure"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've only changed the commented line (26), i hope you didn't mean the "main menu text" as well (line 25)

> Note that you can set the memory limit to a value of your choosing, with a recommended minimum of 256M

### Update anonymization

By default, Dotkernel API uses "soft delete" for it's `User` entities in order to preserve the database entries.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need this much spacing between these phrases? the other sections also have 3 separate paragraphs, but i think it's better to merge them as they are on a single topic

Starting from version 5.3 the `isDeleted` property has been removed because, by default, there is no use in having both it and the status property.

As such, a new `Deleted` case for `UserStatusEnum` is now used to mark a deleted account and remove the redundancy.

* [BC Break] Remove the `isDeleted` property from the `User` class, alongside all usages, as seen in the [pull request](https://github.com/dotkernel/api/pull/359/files)
* Add a new "deleted" case to `UserStatusEnum`, which is to be used instead of the previous `isDeleted` property
* Update the database and it's migrations to reflect the new structure
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change "it's" to "its"

Signed-off-by: Jurj-Bogdan <[email protected]>
Signed-off-by: Jurj-Bogdan <[email protected]>
@arhimede arhimede merged commit 2e18076 into main Jan 20, 2025
10 checks passed
@alexmerlin alexmerlin deleted the issue-84 branch May 6, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document upgrade from 5.2.0 to 5.3.0 following symfony model
3 participants