I have a custom component, that embeds the upload control (the “simple” one):
Now I want to be able to set the allowed extensions via a property (so that in some cases only allow images and in others PDFs). But the extensions property of the control is not bindable?!
How do I come about this? As I really don’t want multiple internal upload controls for each type.
/Henrik
Try Custom, it should pull out a field, I’m not sure if it’s bindable tho. If not then you simply can fork it and set the bindable flag to true, but I’d rather avoid that.
Nope, not even acceptCustom is bindable. Forking seems to be the only solution. Thx.
While WeWeb made forking components stupid simple now, I’d rather not do it anywhere possible.
That’s because the act of forking a components while has a ton of flexibility, takes away from you any future updates to the component. Unless you of course want to manually merge the changes and resolve possible conflicts, which if I’m right is not a feature in the WeWeb’s editor.
I feel like these little things could be solved by making everything bindable by default, but that often requires a lot or wiring behind the scenes.
I 100% agree - but I guess for this very simple control, I can manage the updates manually 
