-
Notifications
You must be signed in to change notification settings - Fork 259
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
Feathr UI feedback #272
Comments
Could we add: source should be clickable and have its own page like features. The source page should display all features belong to this source of a project. |
Can we also add this one?
|
Thanks for feedback, this has been appended to the list in description. |
Thanks for feedback, this has been appended to the list in description. |
Consider adding metadata health and owners information |
This PR update ui code to align with latest api spec which abstracts common interfaces among different registration providers. This PR also enhances lineage ux experience and adds RBAC experience for flighting. New Feature registration API integration API spec can be viewed at https://feathr-registry.azurewebsites.net/docs. UI code is now purview free. UX improvements When a feature is clicked, the feature node is highlighted When a feature is clicked, the feature level lineage path is highlighted. Feature level lineage means direct producer and consumer. Nodes in graph are colored grouped by feature type. User can toggle graph to filter by feature type. Flow arrow is enabled to indicate producer and consumer relationship All out of scope resources are removed in graph, for example, Altas Process, Project. Add navigate button in node so user can click to navigate to feature detail page. RBAC in flgihting, accessible via /management path. Linked issue: #272
Closing this long UI MVP feedback list as most of them are already addressed. For remaining uncompleted items, new issues are opened for tracking separately. |
This issue is opened for tracking feedbacks received for Feathr UI so far
Preview site
https://brave-moss-045d2ce00.1.azurestaticapps.net
Feedbacks
The text was updated successfully, but these errors were encountered: