cc17 / angular-formly Goto Github PK

Formly for Angular is an AngularJS module which has directives to help customize and render JSON based forms. The directive originated from a need to allow our users to create surveys and distribute them easily. Currently we've can render the form data from JSON and assign a model to form so we can receive the submitted data.

	<formly-form result="formData" fields="formFields" options="formOptions" ng-submit="onSubmit()">
	</formly-form>

• Required to use Formly:

• Angular

• Dev dependencies to build Formly

• npm

See bower.json and index.html in the master branch for a full list / more details

• Install with Bower
  $ bower install angular-formly --save

• Include the javascript file in your index.html, Formly comes in the following flavors:

• No templates: you provide all your custom templates using the formlyConfigProvider

<script src="bower_components/angular-formly/dist/formly.min.js"></script>

• Vanilla: no fancy styling, just plain html

<script src="bower_components/angular-formly/dist/formly.vanilla.min.js"></script>

• Bootstrap: bootstrap compatible forms, form-groups, etc.

<script src="bower_components/angular-formly/dist/formly.bootstrap.min.js"></script>

• DIY: Regardless of which flavor you use, you can create your own templates with formlyConfigProvider. Use any of the builds above and override all the templates or just the ones you need.

• Add 'formly' as a required module to your angular app, usually in app.js:
  var app = angular.module('app', ['ng', 'ui.router', 'formly']);

Note: This README.md is for the latest version of formly. There have been some changes in the latest version which is not stable. For documentation on the latest stable version, see the 0.0.16 documentation

You can add a formly-form in your HTML templates as shown below.

	<formly-form result="formData" fields="formFields" options="formOptions" ng-submit="onSubmit()">
		<button type="submit">Hello World</button>
	</formly-form>

Example data as it would be set in the controller

	$scope.formData = {};
	$scope.formFields = [
		{
			//the key to be used in the result values {... "username": "johndoe" ... }
			key: 'username',

			type: 'text',
			label: 'Username',
			placeholder: 'johndoe',
			required: true,
			disabled: false, //default: false
			description: 'Descriptive text'
		},
		{
			key: 'password',
			type: 'password',
			label: 'Password',
			required: true,
			disabled: false, //default: false
			hideExpression: '!username' // hide when username is blank
		}

	];

	$scope.formOptions = {
		//Set the id of the form
		uniqueFormId: 'myFormId'
	};

	$scope.onSubmit = function() {
		console.log('form submitted:', $scope.formData);
	};

Forms can be customized with the options below.

When constructing fields use the options below to customize each field object. You must set at least a type, template, or templateUrl.

type is the type of field to be rendered. Either type, template, or templateUrl must be set.

null

text, textarea, radio select number checkbox, password, hidden, email

template can be set instead of type or templateUrl to use a custom html template form field. Should be used with one-liners mostly (like a directive). Useful for adding functionality to fields.

undefined

templateUrl can be set instead of type or template to use a custom html template form field. Set a path relative to the root of the application. ie directives/custom-field.html

undefined

By default form results are keyed by location in the form array, you can override this by specifying a key.

undefined

label is used to add an html label to each field.

A default is set for each field based on its type. ie Text, Checkbox, Password

required is used to add the required attribute to a form field.

undefined

requiredExpression is used to conditionally require the input. Evaluates on the result and uses the required property on the field.

undefined

hideExpression is used to conditionally show the input. Evaluates on the result and uses the hide property on the field.

undefined

hide is used to conditionally show the input. When true, the input is hidden (meant to be used with a watch).

undefined

disabled is used to add the disabled attribute to a form field.

undefined

placeholder is used to add placeholder text to some inputs.

undefined

description is used to add descriptive text to all inputs.

undefined

data is reserved for the developer. You have our guarantee to be able to use this and not worry about future versions of formly overriding your usage and preventing you from upgrading :-)

undefined

watch has two properties called expression and listener. The watch.expression is added to the formly directive's scope. If it's a function, it will be wrapped and called with the field as the first argument, followed by the normal arguments for a watcher. The listener will also be wrapped and called with the field as the first argument, followed by hte normal arguments for a watch listener.

For example:

// normal watcher
$scope.$watch(function expression(theScope) {}, function listener(newValue, oldValue, theScope) {});

// field watcher
$scope.$watch(function expression(field, theScope) {}, function listener(field, newValue, oldValue, theScope) {});

undefined

validators is an object or array of validator objects. A validator has two properties called name and validate. Templates can pass this option to the formly-custom-validation directive which will add a parser to the ngModel controller of the field. The validate property can be a function which is passed the $viewValue of the field and the field's scope. It can also be an expression which will be evaluated with value (the $viewValue), result, and options of the field available. The name property is used as the name of the validity state (the name of the object on $error).

undefined

Below is a detailed description of each form fields and its custom properties.

The text field allows single line input with a input element set to type='text'. It doesn't have any custom properties.

Example text field

	{
		"type": "text",
		"key": "firstName",
		"placeholder": "jane doe",
		"label": "First name"
	}

The textarea field creates multiline input with a textarea element.

lines sets the rows attribute for the textarea element. If unset, the default is 2 lines.

Example textarea field

	{
		"type": "textarea",
		"key": "about",
		"placeholder": "I like puppies",
		"label": "Tell me about yourself",
		"lines": 4
	}

The checkbox field allows checkbox input with a input element set to type='checkbox'. It doesn't have any custom properties.

Example checkbox field

	{
		"type": "checkbox",
		"key": "checkThis",
		"label": "Check this box",
		"default": true
	}

The radio field allows multiple choice input with a series of linked inputs, with type='radio'.

options is an array of options for the radio form field to display. Each option should be an object with a name(string) and value(string or number).

Example radio field

	{
		"key": "triedEmber",
		"type": "radio",
		"label": "Have you tried EmberJs yet?",
		"default": "no",
		"options": [
			{
				"name": "Yes, and I love it!",
				"value": "yesyes"
			},
			{
				"name": "Yes, but I'm not a fan...",
				"value": "yesno"
			},
			{
				"name": "Nope",
				"value": "no"
			}
		]
	}

The select field allows selection via dropdown using the select element.

The default can be set to the index of one of the options.

options is an array of options for the select form field to display. Each option should be an object with a name(string). You may optionally add a group to some or all of your options.

Example select field

	{
		"key": "transportation",
		"type": "select",
		"label": "How do you get around in the city",
		"options": [
			{
				"name": "Car"
			},
			{
				"name": "Helicopter"
			},
			{
				"name": "Sport Utility Vehicle"
			},
			{
				"name": "Bicycle",
				"group": "low emissions"
			},
			{
				"name": "Skateboard",
				"group": "low emissions"
			},
			{
				"name": "Walk",
				"group": "low emissions"
			},
			{
				"name": "Bus",
				"group": "low emissions"
			},
			{
				"name": "Scooter",
				"group": "low emissions"
			},
			{
				"name": "Train",
				"group": "low emissions"
			},
			{
				"name": "Hot Air Baloon",
				"group": "low emissions"
			}
		]
	}

The number field allows input that is restricted to numbers. Browsers also provide minimal ui to increase and decrease the current value.

min sets minimum acceptable value for the input.

max sets maximum acceptable value for the input.

minlength sets minimum number of characters for the input. If a number less than this value it will not be submitted with the form. eg 1000 is 4 characters long and if minlength is set to 5, it would not be sent. Currently there is no error displayed to the user if they do not meet the requirement.

maxlength sets maximum number of characters for the input. If a number is greater than this value it will not be submitted with the form. eg 1000 is 4 characters long and if maxlength is set to 2, it would not be sent. Currently there is no error displayed to the user if they do not meet the requirement.

Example number field

	{
		"key": "love",
		"type": "number",
		"label": "How much love?",
		"default": 2,
		"min": 0,
		"max": 100,
		"required": true
	}

The password field allows password input, it uses an input with type='password'.

Unlike other formly fields, which use Angular's default setting to trim leading and trailing whitespace, the password field captures whitespace. You can override this by setting trimWhitespace to true.

Example password field

	{
		"key": "password",
		"type": "password",
		"label": "Password"
	}

The hidden field allows hidden input, it uses an input with type='hidden'.

Example password field

	{
		"key": "hiddenCode",
		"type": "hidden"
	}

The email field allows email input, it uses an input with type='email'. Browsers will provide basic email address validation by default.

Example password field

	{
		"key": "email",
		"type": "email",
		"placeholder": "[email protected]"
	}

Formly uses angular's built-in validation mechanisms. See the angular docs for more information on this.

The form name is what you specify on the formly-form directive as the name attribute. If you're using a custom template, to specify a field name use the formly-dynamic-name directive where the value is an expression which would return the name. This expression is only run once, and it is run immediately. Formly will add a formField property to the field, and you can reference that in your template with options.formField to get access to properties like $invalid or $error. See the bootstrap templates for an example.

You can also specify custom validation in your JSON. See the field called validators for more information on this. If you wish to leverage this in a custom template, use the formly-custom-validation directive and pass options.validators to it.

You can configure formly to use custom templates for specified types (your own "text" template) by injecting the formlyConfigProvider in your app's config function. The formlyConfigProvider has the following functions:

Allows you to set a template

formlyConfigProvider.setTemplateUrl('radio', 'views/custom-formly-radio.html');
formlyConfigProvider.setTemplateUrl('checkbox', 'views/custom-formly-checkbox.html');

// the same can be accomplished with

formlyConfigProvider.setTemplate({
	radio: 'views/custom-formly-radio.html',
	checkbox: 'views/custom-formly-checkbox.html'
});

Allows you to get the template

formlyConfigProvider.setTemplateUrl('radio', 'views/custom-formly-radio.html');
formlyConfigProvider.getTemplateUrl('radio') === 'views/custom-formly-radio.html'; // true

Work pretty much the same as the their url counterparts, except they accept an actual template string rather than a url.

Please see the Wiki for tips and tricks from the community.

1. git checkout master
   1. run npm install && bower install
   2. test your code using grunt dev which hosts the app at http://localhost:4000
   3. commit your changes
2. update README, CHANGELOG, bower.json, and do any other final polishing to prepare for publishing
   1. git commit changes

Note: There's a symlink for src and bower_components in the demo and tests folders. Just FYI...

• grunt dev: Creates a server for testing at http://0.0.0.0:4000
• grunt build: Creates the dist
• grunt publish: Copies the src folder and bower_components to gh-pages

When submitting a Pull Request please submit it to the master branch.

Please do the following:

• Follow the existing styles ** Use the third option here: http://blogs.msdn.com/b/cyrusn/archive/2004/09/14/229474.aspx (Thats how we roll)
• Update the README with documentation so people can read how your changes work
• Update the example so people can see how your changes work

• Test! We don't have any...
• Any of the issues in GitHub, let us know if you have some time to fix one.