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

Programmatically set value of parameters inside a partition #143

Open
Airblader opened this issue Sep 24, 2019 · 0 comments
Open

Programmatically set value of parameters inside a partition #143

Airblader opened this issue Sep 24, 2019 · 0 comments
Labels
Comp: Core Core functionality of ngqp Priority: Medium Users can work without this for now, but this should be fixed soon-ish Status: Needs Triage We need to properly tag this issue Type: Bug Something that should work doesn't

Comments

@Airblader
Copy link
Collaborator

Airblader commented Sep 24, 2019

What does the bug look like?

It should be possible to comfortable programmatically set the value of a query parameter inside a partitioned query parameter. There was a user report that there might be issues with that, so we need to triage, verify, fix and add a test for it.

How can this bug be reproduced?

public set max_age(value: number) {
    (this.paramGroup.get('ageRange') as PartitionedQueryParam<number>).queryParams[1].setValue(value);
}

Additional context

What does work is setting the value of the entire partitioned parameter:

public set max_age(value: number) {
    this.paramGroup.get("ageRange").setValue([paramGroup.get("ageRange").value[0], value]);
}
@Airblader Airblader added Type: Bug Something that should work doesn't Comp: Core Core functionality of ngqp Priority: Medium Users can work without this for now, but this should be fixed soon-ish Status: Needs Triage We need to properly tag this issue labels Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Comp: Core Core functionality of ngqp Priority: Medium Users can work without this for now, but this should be fixed soon-ish Status: Needs Triage We need to properly tag this issue Type: Bug Something that should work doesn't
Projects
None yet
Development

No branches or pull requests

1 participant