-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add help policy #26
Comments
@zelenij Do you have an exemple of what you mean? Like having a "?" display near the input where the user can hover it? |
Ok, I see the idea. This is definitely something we could add, we just need to find a clean API to do it. I think it will probably go into the In your example, I can see that it could be a simple string or something more complex with a link etc. Perhaps, we should use a custom DUs: type Help =
| None
| Text of string
| Element of ReactElement I can't think of a good name for the I added the What is your opinion? |
Yes, this is a good start. I'd modify: type Help =
| None
| Text of string
| Component of ReactElement
// Display a help icon and call this event on click
// Maybe add another option, which react to on hover?
| Action of unit -> unit // or accept the mouse click event? |
If we allow the user to provide a In general, I try to avoid providing really specialized callbacks because it quickly end up bloating the library code. Also, it is important to remember that this is (almost?) impossible to provide an universal form logic which works for all the applications in the word. That's why Fable.Form is fully extensible so people can write their own logic and view layer to fit their needs. For example, in all the applications I had to write at work we needed some really specific components. Example speciliazed_form_demo.mp4So often I ended up writing a specific "library" for the needs of that application. |
There should be a way to add detailed help/description to individual form fields
The text was updated successfully, but these errors were encountered: