Developer friendly? Really?
-
What’s not to hate?
Generates terrible bloated markup with tags that don’t belong in HTML spec (like <nf-field>) and have no classes and can’t be assigned custom css classes either. An absolute nightmare to style.
How is having no way of overwriting templates developer friendly? It ISN’T!
How is declaring a class final developer friendly? It ISN’T!
How is having no API for v3 developer friendly? It ISN’T!
I wasted hours on this bag of lies and got to 99% ready with what I was supposed to do and then discovered I have no way on God’s green earth to make SOME elements display on two columns and OTHERS in only one. Turns out I have to BUY AN EXTENSION to do that! Aasdf??aolpsdfg?qopwefasdfczsd!!!!!!!
-
Custom HTML5 Elements (Specification)
https://www.w3.org/TR/custom-elements/Overriding Field Templates
https://developer.ninjaforms.com/codex/custom-field-templates/v3 Forms API (and more)
https://developer.ninjaforms.com/codex/forms/Helper Classes for Field Columns (FREE)
https://ninjaforms.com/docs/styling-your-forms/User Support (Free)
https://ninjaforms.com/contact/Developer Support (Free)
https://developer.ninjaforms.com/slack/
- The topic ‘Developer friendly? Really?’ is closed to new replies.
