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
In order to support the snippet syntax in editors without builtin snippet functionality, and also in order to support variables beyond those specified in the specification, variables (eventually) will have to be handled by sniper itself.
this also adds a much needed layer to the parsing logic. Right now the parsing is only handled on the first call of the snippet, modifying it so that future calls won't have to rebuild a snippet composed of snippets. But variable handling(along with static text transformations), will have to be handled per call.
The text was updated successfully, but these errors were encountered:
In order to support the snippet syntax in editors without builtin snippet functionality, and also in order to support variables beyond those specified in the specification, variables (eventually) will have to be handled by sniper itself.
this also adds a much needed layer to the parsing logic. Right now the parsing is only handled on the first call of the snippet, modifying it so that future calls won't have to rebuild a snippet composed of snippets. But variable handling(along with static text transformations), will have to be handled per call.
The text was updated successfully, but these errors were encountered: