Introduce regex to parse alephium.config.ts
#277
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
Using regex allows only to use simple configurations as it can't understand TS code, so no env variable or functions can be used to define the config value we are parsing here.
tdroxler
force-pushed
the
alephium_config_ts_tranformer
branch
from
4780e2d to
1ec5ad0
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.
Based on this PR #239
We use regex to extract config from
alephium.config.tsRegex only allows to use simple configurations as it can't understand TS code, so no env variable or functions can be used to define the config value we are parsing here.
Currently we don't report error if we can't extract anything from
alephium.config.tsand fallback on current or default config.