Add Request Stamping Functionality to Server and Browser SDK #410
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.
Summary & Motivation
This PR adds functionality to
sdk-browser
andsdk-server
to generate and return stamped requests of each call.It does this by updating the
codegen.js
files in each package to generate stamping versions of each basic method that is effectively a call to the Turnkey API, returning the stamped request WITHOUT actually sending the request.How I Tested These Changes
Tested by creating a stamps using the new functions created in
sdk-server
and then using those stamped requests to successfully make requests to the Turnkey API.Did you add a changeset?
YES -- a changeset has been added!
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
pnpm changeset
.pnpm changeset
will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.