allow non-id columns to be nullable when using foreign #486
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.
Hello @jasonmccreary hope to find you well.
I think I found an issue with
Blueprint
when using foreigns.So here is the scenario, given the following
yaml
file:This would produce the following migration:
Blueprint does handle the nullable modifier well when the column dataType is
id
as you can see here:blueprint/src/Generators/MigrationGenerator.php
Line 328 in e446a41
After that, it checks and removes nullable from the modifier list as it was already handled:
blueprint/src/Generators/MigrationGenerator.php
Line 210 in e446a41
For
non-id
dataTypes (something in my example) it also removes thenullable
modifier, and it shouldn't because those cases are not handled by Blueprint in prior code.I've also added tests to prove this use case.
Let me know if I missed something here.
Best,
Pedro