sebastienros/esprima-dotnet issues and pull requests

#338 - Allow attaching user-defined data to nodes without dictionary lookup

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 6 comments

#337 - Add SyntaxElement internal data set and get API

Pull Request - State: closed - Opened by lahma almost 2 years ago - 9 comments

#336 - Issue with spread/rest operator

Issue - State: closed - Opened by CharlieEriksen almost 2 years ago - 3 comments

#335 - How to get Body.Range from Node?

Issue - State: closed - Opened by nmicun almost 2 years ago - 2 comments

#334 - Update and enhance sample project

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#333 - A few additional minor corrections

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 3 comments

#332 - Enhanced sample project

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#331 - Allow end users to observe JSX token's value

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#330 - Missing ECMAScript 2020+ features

Issue - State: closed - Opened by adams85 almost 2 years ago - 18 comments

#329 - Minor code quality/consistency improvements

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 1 comment

#328 - Improve Token layout and reduce stack frame size for hot paths

Pull Request - State: closed - Opened by lahma almost 2 years ago - 14 comments

#327 - Revision of parser public API

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 5 comments

#326 - Big drop in possible maximum value of MaxAssignmentDepth

Issue - State: closed - Opened by adams85 almost 2 years ago - 4 comments

#325 - Clean up string matcher output in cases where no single-character discriminator exists

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 2 comments

#324 - Use separate StringMatcher for TryGetInternedString

Pull Request - State: closed - Opened by lahma almost 2 years ago - 10 comments

#323 - Implement Parse/TryParse in Range, Position and Location

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 3 comments

#322 - Optional chaining-related parser issues

Issue - State: closed - Opened by adams85 almost 2 years ago
Labels: bug

#321 - Add a way to parse string into Location

Issue - State: closed - Opened by adams85 almost 2 years ago

#320 - Fix bracketing of optional chaining expressions in AstToJavascriptConverter

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#319 - Improve StringMatcher generated code performance

Pull Request - State: closed - Opened by lahma almost 2 years ago - 3 comments

#318 - Further parser optimizations

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 1 comment

#317 - Clean up generation logic and output of StringMatcher

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 6 comments

#316 - Experimenting with spans and StringSegment

Pull Request - State: closed - Opened by lahma almost 2 years ago - 3 comments

#315 - Support ROS input and returning matched string in StringMatcher

Pull Request - State: closed - Opened by lahma almost 2 years ago

#314 - Implement string pooling in scanner/parser

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 8 comments

#313 - Reduce memory allocations in JavaScriptParser

Pull Request - State: closed - Opened by lahma almost 2 years ago - 9 comments

#312 - Improve ToString() formatting in Range and Location

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#311 - Minor improvements to AST

Pull Request - State: closed - Opened by adams85 almost 2 years ago

#310 - Refinements around tokens and comments

Pull Request - State: closed - Opened by adams85 almost 2 years ago - 3 comments

#309 - Remove invalid hash addition to private identifier name

Pull Request - State: closed - Opened by lahma almost 2 years ago - 5 comments

#303 - Eliminate JavaScript letter casing inconsistencies

Issue - State: closed - Opened by adams85 almost 2 years ago - 12 comments
Labels: code-quality

#300 - A few additional rough edges to polish for v3

Issue - State: closed - Opened by adams85 almost 2 years ago - 11 comments

#275 - NodeCollection constructors not public

Issue - State: closed - Opened by CharlieEriksen about 2 years ago - 32 comments

#267 - Use Verify when checking AST compliance

Issue - State: closed - Opened by lahma about 2 years ago - 2 comments

#266 - Change Token to be a struct

Issue - State: closed - Opened by lahma about 2 years ago - 2 comments

#265 - Fix class-related parsing problems

Issue - State: closed - Opened by lahma about 2 years ago - 10 comments

#248 - Class parsing improvements

Pull Request - State: closed - Opened by lahma about 2 years ago - 6 comments

#229 - ESTreeParser

Issue - State: closed - Opened by xp44mm over 2 years ago

#227 - the End Position more than 1 character on comment

Issue - State: closed - Opened by xp44mm over 2 years ago - 1 comment

#198 - Source map support

Issue - State: open - Opened by thautwarm over 2 years ago
Labels: enhancement

#157 - Parse from JSON?

Issue - State: open - Opened by ejsmith about 3 years ago - 2 comments
Labels: enhancement

#149 - ParserException: 'Unexpected token ILLEGAL' on nested templates

Issue - State: closed - Opened by MaceWindu over 3 years ago - 4 comments

#140 - Any API docs?

Issue - State: open - Opened by GF-Huang over 3 years ago
Labels: enhancement

#73 - AST visitor that raises events on node visits

Pull Request - State: closed - Opened by atifaziz over 5 years ago

#70 - JavaScriptParser.ParseProgram throws ArgumentOutOfRangeException

Issue - State: closed - Opened by Metalnem over 5 years ago - 1 comment
Labels: bug

#68 - Replace BCL list for AST with a publicly read-only list

Pull Request - State: closed - Opened by atifaziz over 5 years ago - 7 comments

#44 - Unexpected token ILLEGAL on regex \.

Issue - State: open - Opened by JarLob almost 6 years ago - 13 comments

#40 - Comments are not handled at all?

Issue - State: closed - Opened by KvanTTT almost 6 years ago - 3 comments

#39 - Attach leading and trailing comments to AST nodes

Issue - State: open - Opened by KvanTTT almost 6 years ago - 7 comments
Labels: enhancement

#38 - Implement convenient ToString() methods for nodes and locations

Issue - State: closed - Opened by KvanTTT almost 6 years ago - 3 comments

#37 - Incorrect parse tree during several destructing assignment statements parsing

Issue - State: closed - Opened by KvanTTT almost 6 years ago - 5 comments

#22 - Use System.Span

Issue - State: closed - Opened by lahma about 6 years ago - 8 comments

GitHub / sebastienros/esprima-dotnet issues and pull requests