Conditional fields
planned
Aurélien Georget
Hey everyone 👋
It's Aurélien from Strapi, we added this in our roadmap for next year. So far, it's scheduled that we would start working on it in in Q2 and expect a delivery in Q3 (August). Please continue to post your use cases, the more you share, the better it is for us to adjust the solution to your problems.
✌️
B
Bahadır Yaren
Here are a few more thoughts on the mandatory fields, perhaps from a different perspective. The fields where you cannot create an entry if the field is empty
In the image component of Next.js, the width and height props are required, unless fill prop is set to true.
See the documentation on https://nextjs.org/docs/app/api-reference/components/image#fill.
Some may need to define aria-labels, but either one of aria-label or aria-labelledby.
I can imagine a grouping of required fields where one set of fields is mandatory.
Kuba Raźny
any news?
Jonathan Hsu
Excited for this feature. It has the opportunity to tremendously increase the robustness of the data that can be stored via Strapi while maintaining a high level of data integrity (through the conditional fields). I have a lot of experience in building complex data collection forms that use formulas, visibility conditions, and field validation so I'm happy the Strapi team in any way I can.
Derrick Mehaffy
planned
A
Alex Bennett
Derrick Mehaffy: this update notification got me excited.
Aurélien Georget
Hey everyone 👋
It's Aurélien from Strapi, we added this in our roadmap for next year. So far, it's scheduled that we would start working on it in in Q2 and expect a delivery in Q3 (August). Please continue to post your use cases, the more you share, the better it is for us to adjust the solution to your problems.
✌️
L
Laurens Kling
Aurélien Georget: This is great to hear <3 The use case is pretty simple. Lets say you have a Background component. You have a select box for what kind of background it is, a primary color, etc, or a custom color. Now when the user select custom color you want to show an input to add that custom color string. Right now, that input will always be there, but it will never make sense to be there outside of the custom color context. This our UI is filled with edge-case inputs which make editing difficult and confusing.
B
Brad Douglas
Aurélien Georget: This is great to hear! I've been waiting for this functionality to be added for a while. My use case is to look at how ACF for WordPress uses Conditional Logic when building out field groups. It exactly what I would expect. One quick use case: I give choices to the content editor (Choice A, B,C), they choose, then the proper fields show up for them to add the content.
B
Brianfbento
Aurélien Georget: Any chance we could include tabs as part of this? :D
Aurélien Georget
Brianfbento: The chances are low, a tab system will be introduced for Draft & Published, we won't offer any extension possibilities for the first iteration, however, the component is here and it will create future opportunities :)
A
Adwin Ang
This would make a lot of solutions so much more elegant
K
Kathy
This feature would be very helpful!
L
Lauge Milling
Critical need. Is there anyone who has a solution based on lifecycles or other hacks?
Daan de Gooijer
Lauge Milling: would love a solution as well.
Aaron Ho
Support for relation fields would be great to be able to establish content hierarchy
Josh Davenport-Smith
Absolutely vital feature
Load More
→