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

[EDMTP-281] DependsOn: add fill-select option #282

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

nattallius
Copy link

No description provided.

@nattallius nattallius requested a review from ala-n February 7, 2022 15:16
@github-actions
Copy link

github-actions bot commented Feb 7, 2022

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@nattallius nattallius requested review from smiakchilo and ala-n and removed request for ala-n and smiakchilo February 7, 2022 19:48
@nattallius
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

github-actions bot added a commit that referenced this pull request Feb 7, 2022
@nattallius nattallius marked this pull request as ready for review February 10, 2022 14:59
/**
* Refreshes the options set of a Coral3 Select widget with provided values
*/
public static final String FILL_SELECT = "fill-select";
Copy link
Collaborator

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) {
Copy link
Collaborator

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

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