fix(script): build javascript-algoliasearch after other clients
#223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy Preview for api-clients-automation canceled. 🔨 Explore the source changes: 229cd11 🔍 Inspect the deploy log: https://app.netlify.com/sites/api-clients-automation/deploys/6220c92d67bd11000751c36c |
millotp
reviewed
Mar 3, 2022
shortcuts
added a commit
that referenced
this pull request
Apr 22, 2022
This was referenced May 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
bug nb 1239234 regarding
javascript-algoliasearchAs the JavaScript
algoliasearchclient needs generated clients to be built, we can encounter race issue when clients are not built in the right order.This PR exclude the
javascript-algoliasearchclient from the generators and runs it after.🧪 Test
CI :D