v6.0.0 builds upon the work from v5.0.0 with its own set of breaking changes.
High level changes
Breaking
- Elements are now Subcomponets
- Subcomponent meta data now has a Level
- Renamed ItemType to ViewType in rendering logic
Other
- The Default View Path Helper logic has been moved to an abstract class. This is to help developers who would like to modify certain aspects of the view path helper system without having to rewrite the whole class.
- Section has been moved to MetaData and a selection of methods have been added to support developers who need to use this;
- HasSection - returns a bool if Section has a value
- IsSection - returns a bool if Section meets a specific criteria. There are 3 overloads to support this
In-depth Breaking Changes
Goodbye Elements, hello Subcomponents!
The biggest breaking change is Elements are now called Subcomponents. Elements as a term was a little too vague. Subcomponents will hopefully convey that they exist only to be a part of something else. This isn't the same as a component which can be rendered within another component. If that nested component can existing as its own separate thing then it's still a component.
All tag helpers and logic for Elements has been updated too.
Subcomponents now have a Level
Generally speaking a Subcomponent won't really care about the level but if the subcomponent has components within it like a Grid implementation then the level should be passed through. This may also be useful if you're creating a nested menu using the drop-subcomponent tag helper.
ItemType renamed to ViewType
The name item type or {ItemType} was a little too generic. This was renamed to {ViewType} in the token replacement. As with v5 if you do not wish to break your views down by type this can be omitted by renaming it from the view path pattern in the config.