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

chore: Remove duplicated tags #4580

Merged
merged 1 commit into from
Aug 28, 2023
Merged

chore: Remove duplicated tags #4580

merged 1 commit into from
Aug 28, 2023

Conversation

gastonfournier
Copy link
Contributor

About the changes

At #4432 we've introduced the same tags twice which causes issues when generating the api clients.

Closes #2-1350-fix-openapi-duplicated-tags

@vercel
Copy link

vercel bot commented Aug 28, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments
Name Status Preview Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Aug 28, 2023 11:54am
unleash-monorepo-frontend ⬜️ Ignored (Inspect) Aug 28, 2023 11:54am

Copy link
Member

@nunogois nunogois left a comment

Choose a reason for hiding this comment

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

LGTM!

@gastonfournier gastonfournier merged commit ae18c3d into main Aug 28, 2023
10 checks passed
@gastonfournier gastonfournier deleted the no-duplicated-tags branch August 28, 2023 12:04
thomasheartman added a commit that referenced this pull request Sep 1, 2023
This change sorts the tags in the tags file. This makes it easier to
find tags in the file.

#4580 already introduced a test to check that we have no duplicate
tags, so this isn't as necessary anymore, but it's still nice to have.
thomasheartman added a commit that referenced this pull request Sep 1, 2023
This change sorts the tags in the tags file and tests that the list is
sorted alphabetically. This makes it easier to
find tags in the file. 

#4580 already introduced a test to check that we have no duplicate
tags, so this isn't as necessary anymore, but it's still nice to have.

It also removes the previous auto-sorting before exporting. This is to
ensure that entries are sorted in the source list. This might seem like
a regression, but it makes it easier to spot near-duplicate tags:

> Despite having the test that validates there are no duplicates, you
can always have Notifications and Notification API by mistake (tags that
mean the same but are different). Keeping the list alphabetically sorted
might help to prevent this before pushing the change to prod. In this
case, we will eventually find out and fix it, so this could be a good
reason to have the list sorted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Where to host the repository
2 participants