-
Notifications
You must be signed in to change notification settings - Fork 17
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
fix(spec): remove tags from specs #415
Conversation
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
does that means we can now use tags to group requests? |
At the spec level it always worked, but at the generation level it's a bit different. The tags are used to output the main API file, and in our case we don't want to have multiples. I believe we could update the custom gens to only have a single output file, but it might be more complicated than that. For now, we just remove |
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-417
Changes included:
Splitting some changes from #413
We don't need tags in specs anymore, as it's defaulted to the name of the client.
🧪 Test
CI :D