Default value in select from schema property

[danyaridiger]

Q	A
Is bugfix?	❌
New feature?	✔️
Is backward-compatible?	✔️
Tests pass?	✔️
Fixed issues	#1566
Updated README/docs?	❌
Added CHANGELOG entry?	❌

[schmunk42]

@germanbisurgi Please have a look.

[germanbisurgi]

I think this was solved in this PR #1565

[danyaridiger]

Seems like not because default value still doesn't substitute from 'property' fields (if it's there).

[germanbisurgi]

@danyaridiger could you open an issue with the steps to reproduce the bug?

[germanbisurgi]

probably related -> example

[schmunk42]

As mentioned in #1566 (comment) property is not part of json-schema or did I miss something?

[danyaridiger]

Then how to correctly specify the initial value for the select?

[danyaridiger]

String and other properties always substitute from "property" field

[germanbisurgi]

To specify the initial value of an editor the default keyword is used like in this example

[danyaridiger]

To specify the initial value of an editor the default keyword is used like in this example

This is fine, but why are strings and other primitives replaced from the property, but the selections/radios/checkboxes were not?
Are you considering the possibility of unifying?

[schmunk42]

This is fine, but why are strings and other primitives replaced from the property, but the selections/radios/checkboxes were not?

@danyaridiger Could you create an example for that I do not really understand what you mean.

[danyaridiger]

This is fine, but why are strings and other primitives replaced from the property, but the selections/radios/checkboxes were not?

@danyaridiger Could you create an example for that I do not really understand what you mean.

I couldn't reproduce this. Seems like @germanbisurgi is right and it was fixed in v2.15.1. My mistake was that i
meant values from startval (not property). Now everything works correctly.

[danyaridiger]

Sorry for this maychem)