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
As a developer I would recommend getting rid of populate
Its purpose is to create variables which can be used instead of block names so that scan can be written: scan(block, ... instead of scan("block", .... But it comes with caveats that when the user changes config they must remember to rerun populate to get new blocks and it is different to the recommended way of running g.cset i.e. cset("block", value). However I do not know the history and so would like to understand its motivation.
Acceptance Criteria
A decision is made on populate and the decision is recorder.
Any needed tickets are generated to make the changes
The text was updated successfully, but these errors were encountered:
Could be worth seeing how use of this would play out in the script server too... not sure if this would work well. Something seems wrong about fixing a syntax preference with assignments…
As a developer I would recommend getting rid of populate
Its purpose is to create variables which can be used instead of block names so that scan can be written:
scan(block, ...
instead ofscan("block", ...
. But it comes with caveats that when the user changes config they must remember to rerun populate to get new blocks and it is different to the recommended way of runningg.cset
i.e.cset("block", value)
. However I do not know the history and so would like to understand its motivation.Acceptance Criteria
The text was updated successfully, but these errors were encountered: