You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
After creating a new formula in node you can see in index.js a bunch of const definitions for each input parameter defined at config.json being passed as arguments to the Run method. So when is too many?
We can use destructing in ES6 a small example would be that:
index.js run(process.env)
formula.js function Run({FOO, BAR}) {}
Improving, whould be nice to have a object and forms to retrieve it (for any type of project). One object called Settings and inside of it we have all possible default configurations for int, string, bool values... And 'forms' of retrieving it already typed. Below you can see a small example in C#:
using(Settings setting = new Settings()) {
int x = setting['PROPX'].GetInt();
string y = settin['PROPY'].GetString();
...
setting['PROPZ'].SetInt(230);
...
}
The text was updated successfully, but these errors were encountered:
After creating a new formula in node you can see in index.js a bunch of const definitions for each input parameter defined at config.json being passed as arguments to the Run method. So when is too many?
We can use destructing in ES6 a small example would be that:
index.js
run(process.env)
formula.js
function Run({FOO, BAR}) {}
Improving, whould be nice to have a object and forms to retrieve it (for any type of project). One object called Settings and inside of it we have all possible default configurations for int, string, bool values... And 'forms' of retrieving it already typed. Below you can see a small example in C#:
The text was updated successfully, but these errors were encountered: