-
Notifications
You must be signed in to change notification settings - Fork 108
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
Impl. typecasting for non-display data #1991
Conversation
117c8ba
to
fc9e662
Compare
af83863
to
c0ea0ca
Compare
b0a8761
to
2fe5ad6
Compare
307378e
to
cbdbb6c
Compare
a48cbc0
to
c754653
Compare
0324611
to
ef666b1
Compare
73564ba
to
4353e14
Compare
Hi @mvorisek Sorry for not being able to review within the last 2 days - I see an issue already with this, as multiple Dropdowns are rendering values wrongly ignoring fully and custom renderRowFunction. E.g. You have a dropdown with this renderRow function:
Then, this line will return the ui/src/Form/Control/Dropdown.php Line 277 in 21ac4a3
It has to be |
@mkrecek234 that was introduced in 4b334a3 (#2168) and related #2165 please submit a separate issue for it with a) link to this post, b) minimal self containing repro, c) expected behaviour/fix, and if you can, PR is welcomed. |
@mvorisek You certainly had reasons why you wanted to drop the possibility to adjust value which I would object, as there are use cases where it is helpful - so it mainly is to revert your changes with regard to not allowing renderRowFunction for models to set value back to where it was before. Can we keep it simple and adjust your unreviewed code like this:
|
Thank you for pointing the issue out. The reason is anything rendered in a custom renderer is wrong as it needs to be processed/parsed when selected - this time, using non-custom parser. So there is more going on and it is your job to do this. |
I adjusted my own code writing a custom parser already so if there is no interest by you or others to keep the old, easy functionality and you are not agreeing on the simplified adjustment, I'm fine keeping it as is. |
Michael, developing a framework is about pursuing robust, logical but easy to use design. If you think there is something to improve, please open a separate issue. |
continue #2168
HTML attributes like
data
should be formatted "more using machine readable format".fix #2015