Replies: 1 comment
-
So I looked into this and managed to actually get it working to a point where all you need to do is just add another attribute. I was wondering if this could be added to the bundle, if that's something you'd be interested in? The reasoning behind this is it allows for seamless upgrades of applications, as fields may not want to be deleted. But you still wish to test your application for needed migrations or changes. In our env. we run an automatic migration test each time an entity folder is touched, so it would not pass otherwise. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I wanted to prevent crashes on old application versions which could occur with a column that's selectable, as far as I can tell there's no simple way to disable a column from being selected? Only from being inserted (
insertable
) and updated (updatable
).The reason why I ask about this is we run a test to check if there are any issues with migrations, or if schema:diff needs any new changes. As the metadata driver from attributes would read a column as deleted if I delete the attributes for columns (which would satisfy my runtimme requirement) it would in turn break the migration test.
As such, I was wondering if there's a simpler way to do it, or if I need to "fake" a column being still present only during migrations through a decorator and some detection of the command being ran.
Beta Was this translation helpful? Give feedback.
All reactions