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
We should have a warning on #form location which says that some input should be defined inside the #form. After that we can bind code action of this warning:
Insert required input forms
Insert all input forms
Click on Insert required input forms code action will insert in:
{#input name="userName" /}
Click on Insert all inputinput forms code action will insert in:
@FroMage I noticed that in your sample renarde application you are using simple HTML input element (<input name=""), I wonder if it is better to use #input ?
In your parser we can get those Qute #input user tag, but we don't parse HTML content (it is a text node for us). If you think it is very important to take care of <input HTML element, it will require for our parser to have the capability to parse HTML.
The text was updated successfully, but these errors were encountered:
Well, the #input tag is not part of Renarde but the TODO app, because it's very tied to the CSS framework in use, which depends on the application.
So, probably better to generate <input name="xx"> tags, which are universal.
@JessicaJHee here some directive to implement this issue. In the qute diagnostic, you need to check if section is #form. In this case you need to get the first parameter of the #form (ex : uri:Login.manualLogin()) and get the RestForm of manualLogin method JavaMethodInfo.
and check if RestParam is a form. At this step you can collect all required RestForm.
To check that required restParam are defined in #form as <input html element, you will need to parse HTML which is not done today but only for #form section. Perhaps it could be interesting to create a FormSection class which extends Section.
Given the
manualLogin
method of renarde controller:According @notblank @restform annotations:
Given this #form in qute template:
We should have a warning on #form location which says that some input should be defined inside the #form. After that we can bind code action of this warning:
Click on
Insert required input forms
code action will insert in:{#input name="userName" /}
Click on
Insert all inputinput forms
code action will insert in:{#input name="userName" /} {#input name="password" /}
@FroMage I noticed that in your sample renarde application you are using simple HTML input element (<input name=""), I wonder if it is better to use #input ?
In your parser we can get those Qute #input user tag, but we don't parse HTML content (it is a text node for us). If you think it is very important to take care of <input HTML element, it will require for our parser to have the capability to parse HTML.
The text was updated successfully, but these errors were encountered: