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

Use _links section to drive available actions on ConfigTableRow #6680

Open
2 tasks
ehuelsmann opened this issue Jul 29, 2022 · 0 comments
Open
2 tasks

Use _links section to drive available actions on ConfigTableRow #6680

ehuelsmann opened this issue Jul 29, 2022 · 0 comments
Assignees
Labels
assigned-to-project Issue resolution has been incorporated into a project type:enhancement Proposed improvement, new feature, or extension -- not a defect
Milestone

Comments

@ehuelsmann
Copy link
Member

Currently, the availability of actions in the rows of the config table configuration items are determined client side based on the roles assigned to the user.

However, according to our framework design, the actions available to the user, must be driven by the API responses. This means that

  • The services should be responding with _links sections on the individual items in the returned collections
  • The client side should tie the availability of the actions to data received in the _links section.
@ehuelsmann ehuelsmann added the type:blocking Deemed "needs to be fixed before the assigned release"; unacceptable regressions or critical bugs label Jul 29, 2022
@ehuelsmann ehuelsmann added this to the 1.10 milestone Jul 29, 2022
@ehuelsmann ehuelsmann self-assigned this Jul 29, 2022
@ehuelsmann ehuelsmann removed the type:blocking Deemed "needs to be fixed before the assigned release"; unacceptable regressions or critical bugs label Aug 23, 2022
@ehuelsmann ehuelsmann modified the milestones: 1.10, 1.11 Nov 26, 2022
@ehuelsmann ehuelsmann modified the milestones: 1.11, 1.12 Aug 25, 2023
@neilt neilt added type:enhancement Proposed improvement, new feature, or extension -- not a defect assigned-to-project Issue resolution has been incorporated into a project labels Nov 30, 2023
@ehuelsmann ehuelsmann modified the milestones: 1.12, 1.13 Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned-to-project Issue resolution has been incorporated into a project type:enhancement Proposed improvement, new feature, or extension -- not a defect
Projects
None yet
Development

No branches or pull requests

2 participants