-
Notifications
You must be signed in to change notification settings - Fork 79
Entry's error text displayed even if there is no ErrorText set #28
Comments
Currently this is by design. It's because if you set the error text and currently don't use up the space, then the view will "jump" when the new view is shown. I felt that was less desirable than having the extra space. |
But that's still a lot of space 😄 Or maybe XfxControls' API consumer will have its own validation system that don't relies on ErrorText. (Verry sorry for being a little insistent, that package is great, but I can't use it because of that and #27. Also, since I'm a bit new to this ecosystem, I don't really know how to fork the project and fix it by myself, testing it in an app, etc). |
so the layout on Android is the default Eventually I want to give the user the option of how to display errors (Default or ToolTip), but I'm not sure when that'll be (#6 is my priority right now). If you use "ToolTip", it won't take up the extra space. I can take a look at #27 to see if there's anything I can do there in the near future... shouldn't be too hard. |
Yes, no problem, thanks for the |
How would you pass the option ToolTip or underline error? As an enum? I would like to contribute but would prefer your input on that so I can do it right. |
Yes, an Enum would be preferable.
and then
If you make it bindable, there's a lot of work to do to change it, so at this point I'm recommending it NOT be bindable. One thing to keep in mind is that iOS doesn't have a mechanism for this at all, so you'll have to add the whole works by hand. Android already has the feature built into the EditText. |
Mmmh, ok. Implementing a Tooltip on iOS is some work. But for now I added a pull request, that should address the original problem in this issue. And it will allow extending by tooltip in the future. So I added the enum:
Allowing to remove any Error display. |
This is fixed in #33, Thanks @RudolfVonKrugstein. Do you guys think we should cut a patch release with these fixes even though #6 and #25 are outstanding? They're pretty high priority. |
I would love a release, but that is just my egocentric view. Now it has all the features I want. |
hi,great work, its possible a release with this fix? |
Just following up, V1.1.1 has been released |
thank you very much |
Bug (Feature Request maybe?)
Expected Behavior
When
ErrorText
is empty/null, then the container that contains the error text disappears.Actual Behavior
The space used for the ErrorText is always there and that eats a LOT of space. I don't know if that's intentional, if it is expected, is it feasible to add a new property like
ShowEmptyErrorBlock
?Steps to reproduce the Behavior
The text was updated successfully, but these errors were encountered: