chore: update conventions to explicitly ban TypeScript enum#236
Merged
chore: update conventions to explicitly ban TypeScript enum#236
Conversation
lcovar
force-pushed
the
BTC-3226/update-conventions
branch
from
77a0c1c to
ca4f248
Compare
lcovar
force-pushed
the
BTC-3226/update-conventions
branch
from
ca4f248 to
f99ceee
Compare
davidkaplanbitgo
approved these changes
Mar 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Convention #3 already said to use
as constarrays, but didn't explicitly call out TypeScriptenumas bad. Enums cause type cast issues when crossing WASM/serde boundaries. Added enum to the "Bad" examples and added WASM/serde reasoning to "Why".BTC-3226