-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve/Fix user interface for attribute completeness #42
Comments
11 tasks
mcauer
added a commit
that referenced
this issue
Sep 30, 2024
Therefore extracted an SimpleIndicatorComponent wich accepts conditional children (based on indicator-key) Refs: #42
mcauer
added a commit
that referenced
this issue
Sep 30, 2024
Therefore extracted an SimpleIndicatorComponent wich accepts conditional children (based on indicator-key) Refs: #42
mcauer
added a commit
that referenced
this issue
Oct 22, 2024
…yling Previously the search bar was not initialized properly when the attribute-completeness indicator was unselected during component initialization. Then search functionality was not available. Furthermore the height of the text input field for the search was not set propertly because it inherited wrong rules from SemanicCSS's .ui.toggle.checkbox input which is actually meant for input[type=checkbox] but matched out input[type=text] from the search dropdown. Refs: #42
mcauer
added a commit
that referenced
this issue
Oct 25, 2024
Therefore extracted an SimpleIndicatorComponent wich accepts conditional children (based on indicator-key) Refs: #42
mcauer
added a commit
that referenced
this issue
Oct 25, 2024
Therefore extracted an SimpleIndicatorComponent wich accepts conditional children (based on indicator-key) Refs: #42
mcauer
added a commit
that referenced
this issue
Oct 25, 2024
…yling Previously the search bar was not initialized properly when the attribute-completeness indicator was unselected during component initialization. Then search functionality was not available. Furthermore the height of the text input field for the search was not set propertly because it inherited wrong rules from SemanicCSS's .ui.toggle.checkbox input which is actually meant for input[type=checkbox] but matched out input[type=text] from the search dropdown. Refs: #42
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
migrated here from: GIScience/ohsome-quality-api#810
The above-mentioned PR provides oqapi backend functionality for the new 'attribute completeness' feature.
A very basic user interface has already been implemented in this project.
The following improvements are necessary:
The text was updated successfully, but these errors were encountered: