prettier / angular-estree-parser Goto Github PK

View Code? Open in Web Editor NEW

16.0 9.0 11.0 5.16 MB

A parser that converts Angular source code into an ESTree-compatible form

License: MIT License

JavaScript 2.99% TypeScript 97.01%

angular-estree-parser's Introduction

angular-estree-parser

A parser that converts Angular source code into an ESTree-compatible form

Changelog

Install

# using npm
npm install --save angular-estree-parser @angular/compiler

# using yarn
yarn add angular-estree-parser @angular/compiler

Usage

import * as ngEstreeParser from 'angular-estree-parser';

const ast = ngEstreeParser.parseBinding('a | b:c');
//=> { type: "NGPipeExpression", ... }

API

parseAction(input: string): AST for (target)="input"
parseBinding(input: string): AST for [target]="input"
parseInterpolationExpression(input: string): AST for {{input}}
parseTemplateBindings(input: string): AST for *directive="input"

Development

# lint
yarn run lint

# build
yarn run build

# test
yarn run test

License

MIT © Ika

angular-estree-parser's People

Contributors

Stargazers

Watchers

Forkers

fisker huntex wallet-bic brodybits rogimerio sosukesuzuki qpc-github quantum-platinum-cloud thorn0

angular-estree-parser's Issues

shorthand property declarations in templates is supported in latest Angular

<div dir [input]="{a, b: 2}"></div>

prettier/prettier#11204

angular/angular#42421

`object?.[0]` not supported

"Safe keyed read" expressions like object?.[0] result in an "Unexpected node undefined" warning.

Repro:

parseBinding("object?.[0]")

This was added in this PR: angular/angular#41911

Introduce new Node types

We should have better struct for case like this https://github.com/prettier/prettier/blob/811eb0a08505c2a1aad4ef9dfae6db8065063dd5/src/language-js/print/angular.js#L91

And this https://github.com/prettier/prettier/blob/811eb0a08505c2a1aad4ef9dfae6db8065063dd5/src/language-js/print/angular.js#L65

Bug: Structural directive + no input + as syntax

We have created:

a structural directive with no input
and are using the assyntax to capture the $implicit value of the template context

The syntax check in html template (vscode) works as expected (no errors):

<button
  *IsEmployee="as isEmployee"
  [disabled]="element.status === 1 || (!isDplEmployee && element.status === 2"
>

But when formatting the html (with prettier) the string NgEstreeParser is pretended to the as statement. Resulting in incorrect syntax:

<button
  *IsEmployee="NgEstreeParser as isEmployee"
  [disabled]="element.status === 1 || (!isDplEmployee && element.status === 2"
>

Expected result:

for the formatter to leave the as statement as is

This seems to be linked to the use of a fake prefix.

Not sure if this is the right place to report this, I'd appreciate any pointers where you think this belongs.

Unexpected node ImplicitReceiver

prettier/prettier#8265

Support Angluar 13

https://github.com/angular/angular/releases/tag/13.0.0

I was not able to add support for it.

Can't work on `@angular/[email protected]`

Seems lots of breaking changes on this version.

`foo( bar)` results in an infinite loop

See prettier/prettier#7942 (comment)

Credits to @fisker for finding this bug.

Dependency deprecation warning: @types/babel__parser (npm)

On registry https://registry.npmjs.org/, the "latest" version (v7.1.0) of dependency @types/babel__parser has the following deprecation notice:

This is a stub types definition. babel__parser provides its own type definitions, so you do not need this installed.

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about @types/babel__parser's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Update peerDependencies for @angular/compiler version 8

This seems to work for me in my own fork of Prettier. I would be happy to raise a PR.

I think it would also be ideal to Travis CI testing with @angular/compiler versions 6, 7, and 8.

I would be happy to raise 1 or more PRs.