-
Notifications
You must be signed in to change notification settings - Fork 145
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 UX to configure resource-instance dt nodes #10666
Labels
Comments
whatisgalen
added a commit
that referenced
this issue
Mar 8, 2024
whatisgalen
added a commit
that referenced
this issue
Mar 8, 2024
whatisgalen
added a commit
that referenced
this issue
Mar 8, 2024
whatisgalen
added a commit
that referenced
this issue
Mar 8, 2024
whatisgalen
added a commit
that referenced
this issue
Mar 8, 2024
6 tasks
whatisgalen
added a commit
that referenced
this issue
Mar 16, 2024
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
…de check for relatedResource.ontologyProperty as proxy for relatable, re #10666
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
whatisgalen
added a commit
that referenced
this issue
Apr 17, 2024
6 tasks
whatisgalen
added a commit
that referenced
this issue
May 8, 2024
whatisgalen
added a commit
that referenced
this issue
May 8, 2024
whatisgalen
added a commit
that referenced
this issue
May 8, 2024
Fixed in #10667 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the UI for a node of datatype resource-instance looks like this:
Given that there's no visual cue to click on it in order to do something, I would assume many users (like myself) are unaware there's a relationship configuration UI hidden behind it. An improvement in UX might look like adding a button or icon in order to visually prompt the user to configure this node.
The text was updated successfully, but these errors were encountered: