Skip to content
Smart, Intuitive forms for Ember.js styled with Bootstrap, Multi layouts and Validation support.
Branch: master
Clone or download
Pull request Compare This branch is 184 commits behind piceaTech:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
addon
app/components
config
tests
vendor
.bowerrc
.editorconfig
.ember-cli
.gitignore
.jshintrc
.npmignore
.travis.yml
.watchmanconfig
LICENSE
LICENSE.md
README.md
bower.json
ember-cli-build.js
index.js
package.json
testem.json

README.md

Ember-Rapid-Forms Build Status Code Climate Ember Observer Score

Rapid, Smart, Intuitive forms for Ember.js styled with Bootstrap & Validation ready.

This is a fork of the original over at https://github.com/indexiatech/ember-forms

Installation & Tutorial

With Ember-CLI:

ember install ember-truth-helpers
ember install ember-rapid-forms

Please visit the documentation for installation & usage documentations: http://piceatech.github.io/ember-rapid-forms

Version Support

The Plugin starting from version 1.0.0 doesn't support ember versions below 1.13. If you need support for this work with a version < 1.0.0 or alternativly use https://github.com/indexiatech/ember-forms

Plugin Development

Running

Running Tests

To test on all ember versions: ember try:testall

  • ember test --server

Building

  • ember build

Contributing

Process of creating a PR

  1. Create PR
  2. Wait for one of the Team members to review change
  3. Respond to feedback
  4. Get changed merged

What a PR should include

A PR should include the following things:

  • Changed Files (duuh)
  • Test(s) showing what was fixed / added / deprecated
  • No failing tests
  • Added Documentation if needed

Issues

  • Make sure you test against master. It may already got fixed
  • Search for similiar issues
  • Provide a JSBin with an example if possible

Contributors

  • Asaf Shakarchi (asaf)
  • Ben Limmer (blimmer)
  • Brandon Parsons (brandonparsons)
  • Felix Fichte (spruce)
  • Jack Matthews
  • Josemar Luedke (josemarluedke)
  • Josh Pfosi (joshpfosi)
  • Michael Latta (TechnoMage)
  • Patrick Ma (fivetwentysix)
  • Pedro Kiefer (pedrokiefer)

Building and updating the Documentation

  1. Build the docs: npm run update-page
  2. Upload the new pages git push origin gh-pages
  3. If you don't have push access create PR (see section about PR)
You can’t perform that action at this time.