Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specified default value behaviour #2723

Merged
merged 1 commit into from
Oct 24, 2019
Merged

Specified default value behaviour #2723

merged 1 commit into from
Oct 24, 2019

Conversation

saenglert
Copy link
Contributor

Summary
The docs for the select widget don't mention the widget behaviour when using object based options.
After some trial and error I think I got it figured out.

Test plan
Ask everyone involved at the office and see if my conclusion is correct.

A picture of a cute animal (not mandatory but encouraged)
Please refer to #2718

On a different/continuative note:
The widgets don't handle their own default behaviour. The control component just gets handed the current value as prop. Where in the cms is this value calculated?

@erquhart
Copy link
Contributor

erquhart commented Oct 24, 2019

Ask everyone involved at the office and see if my conclusion is correct.

😂 solid plan

The widgets don't handle their own default behaviour.

100%, been talking about this for a while. There's not much of a calculation, we're just using an empty string or something. Widgets can control as much as they want though - just a matter of ignoring the props. That's what the markdown widget does, and just reports the latest value back to CMS state.

@erquhart erquhart merged commit 5b2fb61 into decaporg:master Oct 24, 2019
nathankitchen pushed a commit to nathankitchen/netlify-cms-backend-azure that referenced this pull request Feb 24, 2020
vladdu pushed a commit to vladdu/netlify-cms that referenced this pull request Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants