Add runtime configuration warning
See original GitHub issueAdd an implicit parameter to the mount function with sensible default to configure what run time warning. Typical example we should be able so catch:
<input onClick={f}/>
instead of onclick<input clazz="c"/>
instead of class<inpu/>
instead of input<div>foo</div>
instead of foo.toString
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
.NET Runtime config options - .NET | Microsoft Learn
Configuring a run-time option by using an environment variable applies the setting to all . NET Core apps.
Read more >16.4. Run-time Configuration - PostgreSQL
This variable specifies one or more shared libraries that are to be preloaded at server start. A parameterless initialization function can optionally be...
Read more >Runtime Configuration - Manual - PHP
The main purpose is to be able to append additional HTML markup to the error message. error_log string. Name of the file where...
Read more >Runtime Configurator Fundamentals - Google Cloud
The Runtime Configurator feature lets you define and store data as a hierarchy of key value pairs in Google Cloud Platform. You can...
Read more >Managing runtime configuration - Pega Academy
2 Edit the Runtime configuration file · In the upper-right corner of the Settings landing page, click Edit to display the Configuration File...
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 Free
Top 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
It would not have to be an implicit parameter, a regular parameter with default value is also fine.
Aah, I misunderstood the role of the config.
I’m not sure either whether “hot fixing” typos is a good idea. I can see it being occasionally convenient but it in the bigger picture it might allow you to be sloppy, which is bad IMO.
I guess it’s best to leave this up to users. This design
is incredibly flexible and it could be used in a ton of unexpected way to create developer/instrumentation tools. The power could be abused to hot fix typos, but I still think we should go with that.