Feature: Allow script-query variables from runtimeConfig
See original GitHub issueCurrently it is not possible to define query variables at runtime - e.g. in case the same build is used in different environments (gtm_preview).
To solve this, publicRuntimeConfig.gtm.variables
should override gtm.variables
, if set.
P.S.: I’ve got it working since the “id” param is not url-escaped 🤫, but that seems kind of hacky 😉
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:10
Top Results From Across the Web
16.4. Run-time Configuration - PostgreSQL
This feature is disabled by default. To enable it, set the vacuum_cost_delay variable to a nonzero value. vacuum_cost_delay (integer). The length of time,...
Read more >gcloud beta runtime-config configs variables get-value
gcloud beta runtime-config configs variables get-value NAME --config-name = CONFIG_NAME [ GCLOUD_WIDE_FLAG … ] DESCRIPTION: (BETA) This command prints only ...
Read more >How to set configuration variables in Next.js | by Eric Burel
Let's start with the simplest pattern. 1) Import the value from a file. Yeah, you don't have to do everything using Next.js features....
Read more >Configure your environment | Cloud Functions for Firebase
When deploying a function with parameterized configuration variables, the Firebase CLI ... while still allowing easy access from your functions when needed.
Read more >next.config.js: Runtime Configuration
Please use environment variables instead in order to avoid initialization overhead. ... Place any server-only runtime config under serverRuntimeConfig .
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sergiobellon this is a workaround:
correct @kissu