Conversation
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
Member
Author
|
@arhimede @MarioRadu @pinclau Found the issue... |
Member
But why that is an issue ? |
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
Member
Author
Correction: It was this old hack we added ages ago. |
Member
Author
|
One small issue to note: in the migration, the |
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>
arhimede
approved these changes
Feb 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@MarioRadu @pinclau If you have time to take a look at this PR, it would be helpful.
I followed the same steps as with dotkernel/api#339 but can't figure out what is missing.
The issue is the the same we had before when we tried implementing enums.
Running the command:
will create a new migration even if there were no changes in the entities, with this
up():and
down():Emptying Doctrine cache did not solve the problem.
Any feedback is welcomed!