Rewrite upgrades bobtemplates.plone style to get a better overview. #223
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.
From the discussion in #222 (comment)
ale-rt 13 hours ago
Can we have something like https://github.com/plone/plone.app.upgrade/blob/f42a09f47173aff76b338ba18ae9fff0dda3b207/plone/app/upgrade/v52/configure.zcml#L7
Which keeps the upgrade steps all together but has a separate include for the upgrade profiles.
Just to be standardish :)
@thet
thet 10 minutes ago Author
As discussed in the chat, I'd prefer the style here - same as here: https://github.com/plone/plone.staticresources/tree/master/src/plone/staticresources/upgrades
It's easier to keep track on what's going on. IMO plone.app.upgrades is harder to understand.
However, this is a minor detail ...