Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / h0tk3y/better-parse issues and pull requests
#71 - Is this repo still active?
Issue -
State: open - Opened by jjmark15 13 days ago
#70 - A StringIndexOutOfBoundsException occurs in this library
Issue -
State: open - Opened by nonesong 11 months ago
#69 - Add another example to README.md
Pull Request -
State: open - Opened by lucasnlm about 1 year ago
#68 - Question: how to get line/column numbers?
Issue -
State: closed - Opened by TheZipCreator over 1 year ago
- 1 comment
#67 - Kotlin 1.9.0 support and usage of Kotlin Common Regex implementation
Pull Request -
State: open - Opened by avwie over 1 year ago
- 4 comments
#66 - Parser works in JS development mode but not in JS production mode
Issue -
State: open - Opened by avwie over 1 year ago
- 2 comments
#64 - "null cannot be cast to non-null type" when parsing generates > 16 token matches
Issue -
State: open - Opened by nikclayton over 1 year ago
- 3 comments
#63 - Indentation as in YAML
Issue -
State: open - Opened by OnufryKlaczynski over 1 year ago
- 3 comments
#62 - Library is not visible in multiplatform project (specifically js and common modules)
Issue -
State: open - Opened by llesha over 1 year ago
#62 - Library is not visible in multiplatform project (specifically js and common modules)
Issue -
State: open - Opened by llesha over 1 year ago
#62 - Library is not visible in multiplatform project (specifically js and common modules)
Issue -
State: open - Opened by llesha over 1 year ago
#61 - How to do recursion?
Issue -
State: open - Opened by JohnLCaron over 1 year ago
#61 - How to do recursion?
Issue -
State: open - Opened by JohnLCaron over 1 year ago
#61 - How to do recursion?
Issue -
State: open - Opened by JohnLCaron over 1 year ago
#61 - How to do recursion?
Issue -
State: open - Opened by JohnLCaron over 1 year ago
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: closed - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#60 - How to fix the build?
Issue -
State: open - Opened by kevinb9n almost 2 years ago
- 1 comment
#59 - WIP: Negative & positive lookahead; also added MultiCharToken for funsies
Pull Request -
State: closed - Opened by acruise over 2 years ago
#59 - WIP: Negative & positive lookahead; also added MultiCharToken for funsies
Pull Request -
State: closed - Opened by acruise over 2 years ago
#59 - WIP: Negative & positive lookahead; also added MultiCharToken for funsies
Pull Request -
State: closed - Opened by acruise over 2 years ago
#59 - WIP: Negative & positive lookahead; also added MultiCharToken for funsies
Pull Request -
State: closed - Opened by acruise over 2 years ago
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#58 - Negative lookahead?
Issue -
State: open - Opened by acruise over 2 years ago
- 9 comments
#57 - RegexToken in Kotlin 1.7.0 JS IR compiler broken due to minification of member names
Issue -
State: open - Opened by qwewqa over 2 years ago
#57 - RegexToken in Kotlin 1.7.0 JS IR compiler broken due to minification of member names
Issue -
State: open - Opened by qwewqa over 2 years ago
#57 - RegexToken in Kotlin 1.7.0 JS IR compiler broken due to minification of member names
Issue -
State: open - Opened by qwewqa over 2 years ago
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#56 - [BUG] literal token with DefaultTokenizer can't find a match - 'noneMatched'
Issue -
State: closed - Opened by xetra11 over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#52 - fix preprocessRegex function (fixes h0tk3y/better-parse#51)
Pull Request -
State: closed - Opened by InfectedBytes over 2 years ago
- 1 comment
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#51 - RegexToken broken with latest js backend
Issue -
State: closed - Opened by InfectedBytes over 2 years ago
#50 - Indentation and Dedentation
Issue -
State: open - Opened by Cormanz over 2 years ago
- 3 comments
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#49 - reuse parser result in other delegate
Issue -
State: open - Opened by asm0dey almost 3 years ago
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#48 - Fix reported range when an optional parser is lifted to an AST parser
Pull Request -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment
#47 - Misreported range in SyntaxTree for optional parser
Issue -
State: closed - Opened by Thomvis about 3 years ago
- 1 comment