Wow! The addition of Collections is one of the most valuable enhancements so far for building custom and dev components. A simple solution for something that is crucial in many components. Absolutely fantastic work by the RW team. Elements is quickly becoming a mature product in this way.
I cannot get the properties from the collections properties.json file to appear in the main properties.json. How does the latter retrieve the correct data? The identifier key to the collection is set correctly. Are there other keys that I need or need to set in a specific way? The structure is identical to the Tables example from the video and the files on Github.
@Bartje, @logrunner glad you got it sorted, and yes we’ll update the docs to note that you need to register your collection in the properties.json file
How does the main template.html file gets access to the properties of the properties.json file in the collections folder? They do appear in the inspector pane, but do not show up in the edit or preview mode.
You can alt-drag component to duplicate them, but not records from a collection yet — when we have a better UI for managing records you’ll be able to do this!
Great updates, Dan. So many of the functions I have needed (usually via Stacks) are starting to make their way to Elements as components. Super encouraging/exciting.
I just upvoted ‘Tabs’ on the Roadmap; seems like it could be a variant of this component? (Maybe I am simplifying.) Tabs are still an elegant solution to displaying lots of information in an economical (space-wise) fashion.
The addition of Collections is one of the most valuable enhancements so far for building custom and dev components. A simple solution for something that is crucial in many components. Absolutely fantastic work by the RW team. Elements is quickly becoming a mature product in this way.
