Replies: 5 comments
-
|
Hey, thanks for your feedback. For the moment, check what's happening after we call the interpreter: https://github.com/ndabAP/vue-command/blob/main/src/components/VueCommand.vue#L382. You have to mimic that and built in your desired behavior. I can give you a more detailed example in a few days. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, if I understand it correctly, everything you see on a screen is the history where every entry is a component. The query is |
Beta Was this translation helpful? Give feedback.
-
|
You are right with all your statements. Check the example for populating and mutating the history: https://github.com/ndabAP/vue-command/blob/main/src/hosted/App.vue#L18. You can pass an array as history property, which will synchronized by |
Beta Was this translation helpful? Give feedback.
-
|
While it's all cool, the problem I'm experiencing has to do with context. In my project, one of the commands is a vue component that uses |
Beta Was this translation helpful? Give feedback.
-
|
Okay, it seems that tagging each instance of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Great project, thank you!
How can I provide my own interpreter for the component? Here's what I'm trying to do. I'm binding my custom function like that:
:interpretor="myFunc". It's getting called, the code is getting executed. The documentation is vague at this point - all it says is that I must use the properties and exposed functions. Can anyone please provide an example of what to call next to output anything and return to the prompt again? Because callingcreateStdoutfrommyFunchas no effect.Beta Was this translation helpful? Give feedback.
All reactions