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

fix(spec): remove tags from specs #415

Merged
merged 3 commits into from
Apr 22, 2022
Merged

fix(spec): remove tags from specs #415

merged 3 commits into from
Apr 22, 2022

Conversation

shortcuts
Copy link
Member

🧭 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

@shortcuts shortcuts requested a review from a team April 22, 2022 08:29
@shortcuts shortcuts self-assigned this Apr 22, 2022
@shortcuts shortcuts requested review from eunjae-lee and damcou and removed request for a team April 22, 2022 08:29
@netlify
Copy link

netlify bot commented Apr 22, 2022

Deploy Preview for api-clients-automation ready!

Name Link
🔨 Latest commit 2f4ddcb
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/62626d030ab0c800082f2186
😎 Deploy Preview https://deploy-preview-415--api-clients-automation.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@shortcuts shortcuts enabled auto-merge (squash) April 22, 2022 08:29
@algolia-bot
Copy link
Collaborator

algolia-bot commented Apr 22, 2022

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.

eunjae-lee
eunjae-lee previously approved these changes Apr 22, 2022
@bodinsamuel
Copy link
Contributor

does that means we can now use tags to group requests?

@shortcuts
Copy link
Member Author

shortcuts commented Apr 22, 2022

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 tags from specs (non bundled), because it's automatically applied when bundling them

@shortcuts shortcuts disabled auto-merge April 22, 2022 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants