typeUserAttrs: some Values got broken since an earlier Version
See original GitHub issueDescription:
i was using an earlier version of formBuilder from around the end of 2017/ start of 2018. In there i used the an object to inject values via typeUserAttrs. This worked well for me. Now, with the current version (3.1.2) this got broken 😦
(btw. from the documentation doesn’t give information about which options i can change. It would be nice of you, if you could enhance the documentation in this regard.)
Environment Details:
- formBuilder Version: 3.1.2
- Browser: chrome
- OS: Win10
Expected Behavior
the header component accepts additional attributes: id and name
Actual Behavior
it doesn’t
Steps to Reproduce
var options = {
typeUserAttrs: {
header: {
id: {
label: 'id'
},
name: {
label: 'name'
}
}
}
}
var fbEditor = document.getElementById(divName);
$(fbEditor).formBuilder(options);
this is just an excerpt. if more informations are needed i will gladly provide them. Also i do this for several more components such as paragraph.
Screenshot - (optional)
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
kevinchappell/formBuilder - Gitter
It seems I can maybe mimic that behavior using typeUserAttrs and typeUserEvents ... attributes like helper text, required checkbox, value, type, etc.
Read more >typeUserAttrs - jQuery formBuilder
typeUserAttrs. Define custom attributes for field types with this handy option. Attribute input types are generated using the typeof for the value.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Tabssummulani spot on.
Looks like the documentation needs updating. will look further into this over the weekend.
I assume this got done, closing.