Open
Conversation
…utside of the instruction in elegant way
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR
command-builtin/command-context-spec- the first "dynamic" command, which just enclose data inside and gave access via:commando/context. In practice user easily may create it's own context by copying code of this one. To enclose his own , maybe even mutable types/object what can even increase performance. Context have :none dependency, what also dont overload dependency managment logic.This solution is ready architectural solution what indeed help user to concentrate on the flow inside of instruction and hide ennecessary or unsecured stuffs. With help of Registry overriding it may significantly increase perfrormance on the frontend where commando may run in cycle multiple time at a second, because operatoin very cheap by design.