feat(specs): import crawler and usage specs from new world repo
#2598
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 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
shortcuts
commented
Jan 23, 2024
Comment on lines
-55
to
-59
| if (docMethod.summary) { | ||
| // Remove dot at the end of summary for better sidebar display | ||
| docMethod.summary = docMethod.summary.replace(/\.$/gm, ''); | ||
| } | ||
|
|
There was a problem hiding this comment.
we don't need this anymore
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
|
insane ! |
Fluf22
approved these changes
Jan 23, 2024
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:
This PR imports the
crawlerandusagespecs written by @kai687 from the new worlds repository, this allows us to centralizes Algolia specs in a single place which all respect the same writing conventions etc.