grunt-resource-bundle-apply v0.1.3

grunt-resource-bundle-apply

Apply the translated resource bundle to the DUST template and replace the i18n tag

Getting Started

This plugin requires Grunt ~0.4.4

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-resource-bundle-apply --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-resource-bundle-apply');

You can run this task as below:

grunt resource-bundle-apply

The "resource-bundle-apply" task

Overview

In your project's Gruntfile, add a section named resource-bundle-apply to the data object passed into grunt.initConfig().

grunt.initConfig({
  'resource-bundle-apply': {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.format

Type: String Default value: '.properties '

A string value to indicate which format will be used as the resource bundle file, the value is ethier .properties or .json .

options.isDeleteProps

Type: Boolean Default value: false

A boolean value that is used to control whether the generated property file no matter it is JSON or JAVA properties files need to be deleted or not after applying.

options.keepI18nTag

Type: Boolean Default value: true

A boolean value that is used to control whether the i18n tag should be kept or not after the translated resource bundle applying to the DUST file.

Usage Examples

grunt.initConfig({
  'resource-bundle-apply': {
		app: {
			options: {
				format: '.properties',
				isDeleteProps: true,
				keepI18nTag: true
			},
			src: ['resourceBundle/**/*.dust']
		}
	},
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)