ln o gravityforms

ln-o-gravityforms

---

Future development goals for component:

• Finish implementing paged form rendering and logic
• Create paging indicators for the above
• To be able to override the main form template
• Investigate implementing some kind of 'input type override', where a developer can provide methods to render specific input types at the component config level and per-form to enable use of custom directives etc in forms, so:

    Markup:
    <form ln-o-gravity-form="{{vm.formId}}" ln-input-map={{vm.gfParserInputOverrides}}" ln-load-from-api="true"></form>

    Controller:
    vm.gfParserInputOverrides= {
      'select': 'select-to-ul',
      'email': 'ln-m-email-input',
      ...
    }

• There some complexities and compromises in this approach:
  • How would a developer pass any extra parameters to the component?
  • Would it need a set of properties and some template markup passed through?
  • The component would simply replace the original input and leave it in place as far as form structure goes
  • Validation etc would all still be 'default' component behaviour