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

feat(manager-api): add column order index for Api Plans so users can explicitly order plans in UI #2159

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

msavy
Copy link
Member

@msavy msavy commented Jul 5, 2022

@volkflo initial version with UI -- needs a little tidying up + tests before committing, but seems to work well.

Sorry for slowness due to holidays.


Thanks to Florian, Olli, Bastian, Christian, and the team at Scheer PAS for contributing to and sponsoring this enhancement to Apiman.

@msavy msavy marked this pull request as ready for review July 7, 2022 12:34
@msavy msavy requested a review from volkflo July 7, 2022 12:34
@msavy
Copy link
Member Author

msavy commented Jul 7, 2022

@volkflo please review and let me know

@msavy msavy self-assigned this Jul 7, 2022
…explicitly order plans in UI

This feature is used by the API Developer Portal also.

Closes: apiman#1639
@msavy msavy merged commit 75eda35 into apiman:master Jul 7, 2022
@msavy
Copy link
Member Author

msavy commented Jul 7, 2022

Thanks to Florian, Olli, Bastian, Christian, and the team at Scheer PAS for contributing to and sponsoring this enhancement to Apiman.

@msavy msavy changed the title feat(distro-ddl): add column order index for Api Plans so users can explicitly order plans in UI feat(manager-api): add column order index for Api Plans so users can explicitly order plans in UI Jul 7, 2022
Copy link
Member

@volkflo volkflo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if you already merged this, just a question for better understanding:

The reason for not using the new rest endpoint (/reorderApiPlans) from the UI is that it is easier on that page to just update the whole api version?

@msavy
Copy link
Member Author

msavy commented Jul 8, 2022

Even if you already merged this, just a question for better understanding:

The reason for not using the new rest endpoint (/reorderApiPlans) from the UI is that it is easier on that page to just update the whole api version?

It is simply that the UI was already using the existing endpoint in several locations and I could avoid changing any code dealing with that. But to keep the API consistent with the policy chain reordering, and for other use-cases (e.g. CLI), I think it's best to add the reorder endpoint also.

@volkflo
Copy link
Member

volkflo commented Jul 8, 2022

Okay cool, thanks for the comments 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants