Skip to content

Conversation

@markstory
Copy link
Member

Slim down ConfigInterface to only be what we are using.

Slim down `ConfigInterface` to only be what we are using.
public const VERSION_ORDER_EXECUTION_TIME = 'execution';

public const TEMPLATE_STYLE_CHANGE = 'change';
public const TEMPLATE_STYLE_UP_DOWN = 'up_down';
Copy link
Member

@dereuromark dereuromark Aug 7, 2025

Choose a reason for hiding this comment

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

We should probably keep that to allow config switching for #473
this can be a config via Configure, similar to the other ones.

Or is "change" too complicated out of the box? And we stick to up/down always?

Copy link
Member Author

@markstory markstory Aug 8, 2025

Choose a reason for hiding this comment

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

We've never used these constants in the bake commands though. Personally, I stick with up/down.

Edit: I didn't see the link to the other issue asking for support for change() in generated code. I don't think that Config is the place to keep constants that are only relevant during migration generation. A better place would be the command class, or template helpers, and we could add those constants when #473 is fixed.

@dereuromark dereuromark merged commit 8a96b01 into 5.x Aug 8, 2025
13 checks passed
@dereuromark dereuromark deleted the remove-unused-code branch August 8, 2025 12:22
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.

3 participants