-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consumer Flow Creating Issues #19
Comments
I forgot to tag you @hidetak, but do you think you can have a look at these points? Also let me know if these are intended in a way |
After this, I think we can publish the release ;) |
Thanks for the confirmation!
Sorry, the above was a comment about uncertainties regarding Server-side nodes. Your point is only about the Consumer Flow generation functionality.
I thought Property required a type. I'll check to see how it works without a type.
I too thought it would be better to execute it with a button, but the timing of when the text form sends the message needs to be selected from below. Therefore, if it were controlled by a button, the flow would be complicated by the need to temporarily store it in a context. Since this flow also serves as a sample for creating a WoT consumer, I thought it would be better to keep it simple and decided to control it with the enter key. I agree about displaying text when enter is pressed. I will try to fix it.
If multiple UIs are implemented in one flow, they can be selected from the hamburger menu in the upper left corner as shown below. |
Thank you taking a look!
There can be directly an enum or oneOf( or other combinations words) so for properties you can generate a text field if you don't see a type
For actions, you should not generate any form if there's no input but that means we would need a button to invoke. I understand the annoyance it causes and for now we can have a "dummy" text input that says "please click on the text field and press enter to invoke the action"
Alright thanks :) |
An example of Consumer UI is provided.
I will proceed with the implementation here, but I would appreciate any comments you may have. |
@hidetak the direction looks really nice and I do not see any issues at this stage |
@egekorkan |
tdAction.input is undefined
. First, we should be more flexible since not all actions have an input. Second, the error should be pointing to the action if we want to show the error.invoke
button to actions and a message saying "action invoked". Enter gives feedback if the action works as intended but if the action does not work, I cannot be sure if I managed to invoke it in the first place. Something similar would be good for properties and events as well, i.e. "property X read" etc.Otherwise, it works
The text was updated successfully, but these errors were encountered: