export ERTP types and normalize enum pattern #10263
Merged
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
Deploying agoric-sdk with
|
| Latest commit: |
0fa8c9f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://318ef72c.agoric-sdk.pages.dev |
| Branch Preview URL: | https://ta-export-ertp-types.agoric-sdk.pages.dev |
turadg
changed the title
Chris-Hibbert
approved these changes
Oct 11, 2024
A precaution against any runtime-ish symbols being included
turadg
force-pushed
the
ta/export-ERTP-types
branch
from
e7c24be to
f2faed3
Compare
turadg
force-pushed
the
ta/export-ERTP-types
branch
from
f2faed3 to
0fa8c9f
Compare
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.
refs: #4560
Description
Exports ERTP types from the package entrypoint.
Establishes a pattern for constant enums so the type name matches.
Review by commit
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
Upgrade Considerations