Package Exports
- catharsis
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (catharsis) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Catharsis
A JavaScript parser for Google Closure Compiler type expressions.
Catharsis is designed to be:
- Accurate. Catharsis is based on a PEG.js grammar that's designed to handle any valid type expression. It uses a Mocha test suite to verify the parser's accuracy.
- Fast. Parse results are cached, so the parser is invoked only when necessary.
- Flexible. Catharsis can also convert parse results back into type expressions.
Example
var catharsis = require('catharsis');
var type = '!Object';
var parsedType;
var expr;
try {
parsedType = catharsis.parse('!Object');
console.log('%j', parsedType); // {"type":"NameExpression,"name":"Object","nullable":false}
}
catch(e) {
console.error('unable to parse %s: %s', type, e);
}
expr = catharsis.stringify(parsedType);
console.log(expr); // !ObjectSee the test/specs/ directory for more examples of Catharsis' parse results.
Methods
parse(type, opts)
Parse the Closure Compiler type type, and return the parse results. Throws an error if the type
cannot be parsed.
Parameters
type: A string containing a Closure Compiler type expression.opts: Options for parsing the type expression.opts.useCache: Specifies whether to use the cache of parsed types. Defaults totrue.
Returns
An object containing the parse results.
stringify(parsedType, opts)
Stringify the parsed Closure Compiler type expression parsedType, and return the type expression.
If validation is enabled, throws an error if the stringified type expression cannot be parsed.
Parameters
parsedType: An object containing a parsed Closure Compiler type expression.opts: Options for stringifying the parse results.opts.useCache: Specifies whether to use the cache of stringified parse results. Defaults totrue.opts.validate: Specifies whether to validate the stringified parse results by attempting to parse them as a type expression. Defaults tofalse.
Returns
A string containing the type expression.
Installation
With npm:
npm install catharsisOr without:
git clone git://github.com/hegemonic/catharsis.gitRoadmap and known issues
Take a look at the issue tracker to see what's in store for Catharsis.
Bug reports, feature requests, and pull requests are always welcome! If you're working on a large pull request, please contact me in advance so I can help things go smoothly.
Note: The parse tree's format should not be considered final until Catharsis reaches version 1.0. I'll do my best to provide release notes for any changes.
Changelog
- 0.3.1 (March 2013): Type expressions that begin with a reserved word, such as
integer, are now parsed correctly. - 0.3.0 (March 2013):
- The
parse()andstringify()methods are now synchronous, and theparseSync()andstringifySync()methods have been removed. Note: This change is not backwards-compatible with previous versions. - The parse results now use a significantly different format from previous versions. The new format is more expressive and is similar, but not identical, to the format used by the doctrine parser. Note: This change is not backwards-compatible with previous versions.
- Name expressions that contain a reserved word now include a
reservedWord: trueproperty. - Union types that are optional or nullable, or that can be passed a variable number of times, are now parsed and stringified correctly.
- Optional function types and record types are now parsed and stringified correctly.
- Function types now longer include
neworthisproperties unless the properties are defined in the type expression. In addition, thenewandthisproperties can now use any type expression. - In record types, the key for a field type can now use any type expression.
- Standalone single-character literals, such as ALL (
*), are now parsed and stringified correctly. nullandundefinedliterals with additional properties, such asrepeatable, are now stringified correctly.
- The
- 0.2.0 (November 2012):
- Added
stringify()andstringifySync()methods, which convert a parsed type to a type expression. - Simplified the parse results for function signatures. Note: This change is not backwards-compatible with previous versions.
- Corrected minor errors in README.md.
- Added
- 0.1.1 (November 2012): Added
optsargument toparse()andparseSync()methods. Note: The change toparse()is not backwards-compatible with previous versions. - 0.1.0 (November 2012): Initial release.