-
Notifications
You must be signed in to change notification settings - Fork 13
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
[EDMTP-281] DependsOn: add fill-select option #282
base: develop
Are you sure you want to change the base?
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
ce939c3
to
16245f5
Compare
I have read the CLA Document and I hereby sign the CLA |
/** | ||
* Refreshes the options set of a Coral3 Select widget with provided values | ||
*/ | ||
public static final String FILL_SELECT = "fill-select"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A question is:
Are we always going to fill only selects? No raidoGroups/ buttonGroups / autocompletes? May it be, we would want to give a more generic name, kind of "fill-options"?
* @param {string} option.value - actual value of an option | ||
* @param selectedValue - value or array of values to trigger 'selected' state of the option | ||
*/ | ||
static createOption(option, selectedValue) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update-datasource
action is creating Select options as well. May I kindly ask you to look into that action and possibly implement these methods there? So that we have a more unified codebase
No description provided.