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
changes to scripts.js
dont let users save invalud key or value
move tunables.json and add feature
Document allowed tunables and error handling
Added section on allowed tunables and their validation process.
Exclude tunables.json from RAT and prettier
Copy file name to clipboardExpand all lines: doc/Wiki.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -372,12 +372,21 @@ Tunables are configured using **Key** and **Value** fields in the launch configu
372
372
373
373
Use the **“+ Add Tunable”** button to add additional entries. Each row can be removed using the **“X”** button.
374
374
375
+
Tunables are case sensitive, and only allowed tunables will be allowed to be saved in the wizard.
376
+
375
377
Tunables control runtime behavior and performance characteristics. Most tunables have default values, so you only need to specify a value if you want to override them.
In order to prevent unexpected tunables from being ran, there is a list of allowed tunables at `constants/tunables.json` which contains all valid tunables. Tunables are case sensitive and the values type must match what is expected. For example boolean values will only allow true or false. If a invalid tunable is saved in the `launch.json` , when you attempt to run daffodil you will encounter a error saying `Cancel` or `Ignore invalid tunable`. Cancel will send you back where you fix the error, and Ignore invalid tunable runs daffodil but does not register the invalid tunable. The tunable will stay in your launch.json however. The tunables.json file will be updated as new tunables are added and removed.
// If the user dismisses the checkbox in anyway it will exit. so Cancel , Esc or unexpected values will exit
808
+
// Only pressing ignore invalid tunables will proceed with the launch and remove the invalid tunables from the config sent to the debug adapter
809
+
if(choice!=='Ignore Invalid Tunables'){
810
+
returnundefined
811
+
}
812
+
//Copies the tunables , then deletes the invalid tunables from the copied config so that the user can still see the invalid tunables in their launch.json but they won't be sent to the debug adapter and cause errors
0 commit comments