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

variable-resolver-service should let clients know if variables are not defined #6332

Closed
elaihau opened this issue Oct 7, 2019 · 0 comments
Closed
Labels
variable-resolver issues related to the variable-resolver extension

Comments

@elaihau
Copy link
Contributor

elaihau commented Oct 7, 2019

Description

Breaking changes were made to variable-resolver-service in. It should be reverted and other ways of identifying the undefined input variables implemented.

@elaihau elaihau added bug bugs found in the application variable-resolver issues related to the variable-resolver extension labels Oct 7, 2019
@elaihau elaihau self-assigned this Oct 7, 2019
@elaihau elaihau changed the title breaking changes made to variable-resolver-service in PR 6331 should be reverted variable-resolver-service should let clients know if variables are not defined Oct 7, 2019
@elaihau elaihau removed their assignment Oct 7, 2019
@elaihau elaihau removed the bug bugs found in the application label Oct 7, 2019
@elaihau elaihau closed this as completed Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
variable-resolver issues related to the variable-resolver extension
Projects
None yet
Development

No branches or pull requests

1 participant