fix(api-service): Nv 5379 refinements needed for sdks and api documentation #7835
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 dev-web-novu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
tatarco
changed the title
SokratisVidros
approved these changes
Mar 4, 2025
apps/api/src/app/shared/framework/swagger/open.api.manipulation.component.ts
Outdated
Show resolved
Hide resolved
tatarco
force-pushed
the
nv-5379-refinements-needed-for-sdks-and-api-documentation
branch
from
49c5699 to
42fd2de
Compare
tatarco
deleted the
nv-5379-refinements-needed-for-sdks-and-api-documentation
branch
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 changed? Why was the change needed?
the following represent the code portion in novu
Ask Mintlify why the order of endpoints groups (tags) is different than the source OpenAPI spec by Speakeasy.
Massage Swagger in Novu API to place all V2 endpoints above V1.
Done Here
Fix cancel trigger response on the SDK
Done Here
Refine autogenerated SDK repositories to have Novu description, tags, and updated README.md.
Set description, website, author, license, bugs, fundingInfo to package.json of @novu/api
Add the same branded header to all README files across all packages.
Deprecate @novu/node using npm deprecate. Update readme https://www.npmjs.com/package/@novu/node to point to @novu/api
[ ]Update the docs to point to the new SDKs https://docs.novu.co/platform/sdks/server. ||| Nothing to be done, already done by emil
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer