Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cowboy/grunt-testing123
Whatever
https://github.com/cowboy/grunt-testing123
Last synced: 30 days ago
JSON representation
Whatever
- Host: GitHub
- URL: https://github.com/cowboy/grunt-testing123
- Owner: cowboy
- License: mit
- Created: 2013-06-26T19:54:40.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2016-02-21T17:03:22.000Z (almost 9 years ago)
- Last Synced: 2024-11-14T13:23:51.365Z (about 1 month ago)
- Language: JavaScript
- Size: 113 KB
- Stars: 2
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE-MIT
Awesome Lists containing this project
README
# grunt-testing123
> The best Grunt plugin ever.
## Getting Started
This plugin requires Grunt `~0.4.1`If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
```shell
npm install grunt-testing123 --save-dev
```Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
```js
grunt.loadNpmTasks('grunt-testing123');
```## The "testing123" task
### Overview
In your project's Gruntfile, add a section named `testing123` to the data object passed into `grunt.initConfig()`.```js
grunt.initConfig({
testing123: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
},
},
})
```### Options
#### options.separator
Type: `String`
Default value: `', '`A string value that is used to do something with whatever.
#### options.punctuation
Type: `String`
Default value: `'.'`A string value that is used to do something else with whatever else.
### Usage Examples
#### Default Options
In this example, the default options are used to do something with whatever. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result would be `Testing, 1 2 3.````js
grunt.initConfig({
testing123: {
options: {},
files: {
'dest/default_options': ['src/testing', 'src/123'],
},
},
})
```#### Custom Options
In this example, custom options are used to do something else with whatever else. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result in this case would be `Testing: 1 2 3 !!!````js
grunt.initConfig({
testing123: {
options: {
separator: ': ',
punctuation: ' !!!',
},
files: {
'dest/default_options': ['src/testing', 'src/123'],
},
},
})
```## 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](http://gruntjs.com/).## Release History
_(Nothing yet)_