Replies: 1 comment
-
This is gonna be amazing @Taitava!!! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This idea actually emerged in #127, which discusses about storing shell command output values into custom variables. As custom variables are quite a big concept, and relate to other features too, I created an own discussion for it.
Features that could set values to custom variables
Features that could read the values
Naming conventions for custom variables
{{_
and ends with}}
. The underscore_
prefix avoids possible name collisions between users' custom variables and all the new built-in variables that will be developed for SC in the future, because built-in variables will never use an underscore_
as a prefix.a-z
, numbers0-9
and an underscore_
.{{_my_variable}}
(same as{{_MY_VARIABLE}}
or{{_My_VaRiAbLe}}
){{_x}}
(minimun length variable name)User interface
Other features
{{file_*}}
variables when executing shell commands via events in a situation where no file is active, in which case the execution can be automatically cancelled without error messages.data.json
settings, file, but I'm not yet sure about the format and location (in vault root or in plugin folder? Freely decidable name/path or not?).Variable types
0-9
, all other characters will be silently stripped away. Edit 2022-11-24: Should negative values be supported by allowing-
prefix? Or should there be two integer types: one which supports both positive and negative values, and one that supports only positive?0-9
and a decimal point (a dot.
or comma,
, variable will have a setting for defining if a comma will be converted into a dot, or vice-versa). There will be no support for a thousands separator. In some countries, comma is used as a thousands separator, but it won't work here.2.3e-5
. Should they be supported or not?Beta Was this translation helpful? Give feedback.
All reactions