github-migration
/
coffeescript-support
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed READ typos

This commit is contained in:
Christopher H. Laco 2011-02-02 23:16:17 -05:00
parent 4f20bd0225
commit ac3dd5f69b
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.textile
View File

@ -18,18 +18,18 @@ h2. What it does
This plugin is pretty basic right now. It currently: This plugin is pretty basic right now. It currently:
* Sets Spec.js and SpecHelper.js files to jasmine/javascript fileType * Sets *Spec.js and *SpecHelper.js files to filetype=jasmine+javascript
* Applies basic syntax highlighting for jasmine keywords in addition to normal javascript syntax * Applies basic syntax highlighting for jasmine keywords in addition to normal javascript syntax
* Loads snippets for jasmine filetype for: * Loads snippets for the jasmine filetype for:
** desc: description block with before..it..expect ** desc: description block with before..it..expect
** before: beforeEach block ** before: beforeEach block
** after: afterEach block ** after: afterEach block
** it: it...expect block ** it: it...expect block
** helper: beforeEach block and matcher for SpecHelper.js ** helper: beforeEach block and addMatcher/matcher blocks for SpecHelper.js
** matcher: matcher block for SpecHelper.js ** matcher: matcher block for SpecHelper.js
** expect: expect..to line ** expect: expect..to line
** spy: spyOn method ** spy: spyOn method
* Uses templates for new Spec/SpecHelper buffers * Uses templates for new jasmine buffers
* Runs all specs in jasmine:ci * Runs all specs in jasmine:ci
You can disable templating by setting g:jasmine_use_templates="" You can disable templating by setting g:jasmine_use_templates=""
@ -38,9 +38,9 @@ By default, the plugin assumes the templates are in bundle/jasmine/template and
h2. Running Specs h2. Running Specs
Slowly working on interactive spec running support. Currently, the Jasmine() command is provided for jasmine fileType buffers. When invoke, it searchs the curent/parent directories of that buffer for the nearest Rakefile, then invokes rake jasmine:ci to run all specs. I'm slowly working on interactive spec running support. Currently, the Jasmine() command is provided for jasmine buffers. When invoked, it searches the current/parent directories of that buffer for the nearest Rakefile and invokes rake jasmine:ci to run all specs.
I plan on added Red/Green support, as well as quickfix error support. I plan on adding Red/Green support, as well as quickfix error support.
h2. TODO h2. TODO