Add support for nested, repeating schemas
Any news on this? I have some time to work on this feature.
Antonio Novoselnik: I would also give time for this feature
I would love to have this feature, I am new to Keystone, 1 day to be precise. The first model I created needed this feature.
Not having much luck with the nested-lists branch:
GET /keystone/api/nesteds/57c972672134a2cafd1c69ce?drilldown=true 200 42.274 ms
TypeError: callback is not a function
at nextTickCallbackWith0Args (node.js:420:9)
at process._tickCallback (node.js:349:13)
Anything I can do to help out?
This post was marked as
This is my main concern about using KeystoneJS for story-led sites where the client requires the ability to build out rich case study style pages from sets of front-end components which contain multiple optional and non-optional fields, e.g. gallery blocks, text blocks and video blocks. Wordpress ecosystem has solved this with third-party solutions such as ACF's repeater field, and Processwire and Craft have similar built into the core.
Are there any workarounds that can tie me over until this is implemented?
Not really, although you could make a "block" list that has a page reference, a sequence number and optional fields for all the types you want to support, and then in the page you basically do a find for the blocks applying to the page and add them in order, showing whatever data they have.
Alex Hillel: seriously? u cant search for other appropriate front-end drag drop blah blah? apples and oranges mate..
These kinds of structures are all over our data model. Currently we use keystone.mongoose.Schema.Types.Mixed for these structures. Unfortunately this means they must be read-only & cannot be displayed in the admin ui.