feat(editor): add field option when to be able to show fields conditionally
#1894
Conversation
|
Deploy preview for netlify-cms-www ready! Built with commit f140feb |
|
I'm definitely in favor of the goal here, but we need to think through how to go about it a bit more. We don't support functions in the config, and I'm not sure we want to bake conscript into our API. There's some discussion of this feature in #1267, and I believe a PR was started but didn't get to completion. |
LoicMahieu
force-pushed
the
feature/fields-conditional
branch
from
56a1058 to
3b182b1
Compare
|
Deploy preview for cms-demo ready! Built with commit f140feb |
|
I found Anyway, in my use-case, I don't use this syntax but only the function style. In fact, I configure only by JS, see #1866 |
|
Yeah - I'm not saying it isn't functional, but I'd like to avoid bringing outside specs into our API. For example, Immutable.js is a part of our API right now, meaning folks need to understand how that library works to do any customization in the CMS, and that's a decision I regret (planning to remove it in an upcoming major release). Totally agree on the goal of this PR, we just need to find a different approach. |
|
@LoicMahieu any thoughts on my last comment? |
|
Closing as stale due to lack of activity and/or interest. Please comment if you feel this should be reopened. |
Summary
Add field option
whento be able to show fields conditionally.It could be useful to conditionally show/hide some fields depending on the data. This PR allows to specify a new option
whenwhich could be:conscript.jsfor simple language for writing potentially-complex sets of conditions.Test plan
WIP...