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

StringTagValueFragment: Update model for constraints in keyup #152

Open
hallahan opened this issue May 22, 2016 · 0 comments
Open

StringTagValueFragment: Update model for constraints in keyup #152

hallahan opened this issue May 22, 2016 · 0 comments

Comments

@hallahan
Copy link
Contributor

Right now, we test constraints any time a radio button or check box is selected to hide / show other tags. We only test constraints for the StringTagValueFragment when the user tries to save. This means that if there is a constraint that depends on a StringTagValueFragment, it won't really be seen until the user tries to save.

Right now, I'm not seeing any constraints where this actually matters, but it could become a bug. I'm going to keep this low priority until someone cares.

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

No branches or pull requests

1 participant