We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
IsLoading
In a same way that a field can be disabled, I think adding IsLoading to the field config can make sense.
I am unsure if we should do it the field config level or if it should be at the Attributes level (per case by case).
Attributes
I think slight in favour of doing it as the config level and if a type of field doesn't suppose loading then it can just ignore that property.
Doing it at the config level, imply that Fable.Form will have a Base.setLoading function in it like Base.disable.
Base.setLoading
Base.disable
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In a same way that a field can be disabled, I think adding
IsLoading
to the field config can make sense.I am unsure if we should do it the field config level or if it should be at the
Attributes
level (per case by case).I think slight in favour of doing it as the config level and if a type of field doesn't suppose loading then it can just ignore that property.
Doing it at the config level, imply that Fable.Form will have a
Base.setLoading
function in it likeBase.disable
.The text was updated successfully, but these errors were encountered: