initial draft for template args rules #195
Conversation
| - Use `<name>Override` (object) to extend existing variables/objects | ||
| - Can reference variables in two ways: | ||
| - `$$$variableName` - For variables already defined in template | ||
| - `${variableName}` - For variables defined in your `preConfigContent` |
There was a problem hiding this comment.
as I understand there's no difference if variable is defined inside template or preconfigured content. See #175 , both deployerPrivateKey (used as [$$$deployerPrivatekey]) and providerApiKey (used for example as https://eth-sepolia.g.alchemy.com/v2/\${providerApiKey} defined inside template
For me, the key difference is:
$$$variableName - When we need to remove "" or '' around the variable or expression in resulting object.
Works for any variable types. Examples:
apiKey: "$$$etherscanOptimisticApiKey" => apiKey: etherscanOptimisticApiKey;
accounts: ["$$$deployerPrivateKey"] => accounts: [deployerPrivateKey]
Expression:
enabled: '$$$process.env.MAINNET_FORKING_ENABLED === "true"', => enabled: process.env.MAINNET_FORKING_ENABLED === "true"
${variableName} - when we need to use the variable inside the string. Works for strings and for js stringifyable primitives like number or boolean
| }, | ||
| mainnet: { | ||
| url: `https://eth-mainnet.g.alchemy.com/v2/$$$providerApiKey`, | ||
| accounts: ["$$$deployerPrivateKey"], |
There was a problem hiding this comment.
we need to define deployerPrivateKey somewhere in example
Description:
The initial draft for initial rules.
I think this should probably be merged after #175.
After #175 we can update other config files to follow the same patterns like updating
tailwind.config,nextjs.configetc.