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

Inconsistency in "hint" binding usage in the informal API. #237

Open
kaladay opened this issue Jul 10, 2023 · 0 comments
Open

Inconsistency in "hint" binding usage in the informal API. #237

kaladay opened this issue Jul 10, 2023 · 0 comments

Comments

@kaladay
Copy link
Contributor

kaladay commented Jul 10, 2023

Describe the bug
The expected behavior of the "hint" attribute and its binding is not clearly defined.
Different bindings are in use and this means that the expected "hint" behavior is inconsistent.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the links above.
  2. View the bindings for hint.

Expected behavior
A consistent and defined expected behavior for "hint" and the appropriate binding to match the expected behavior.

The hint attribute on validated inputs of all types should act and behave with the same binding to avoid unexpected behavior, bugs, and regressions in projects utilizing weaver-ui-core.

Documentation of the expected bevavior should be also be provided to formalize the expected API behavior.

kaladay added a commit that referenced this issue Jul 10, 2023
The expected and intended design is unclear.
Revert the binding change so that another issue can be used to follow and address it in greater detail.

The issue created is: #237 .
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