Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

grol-io / grol Public

Notifications You must be signed in to change notification settings
Fork 2
Star 22

Code
Issues 17
Pull requests 3
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Show parsing errors in context of line where they occur#168

Merged

ldemailly merged 5 commits intomaingrol-io/grol:mainfrom parsing_errorgrol-io/grol:parsing_errorCopy head branch name to clipboard

Aug 20, 2024

+95-27

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Aug 20, 2024

Show errors in context of line where they occur
ldemailly
committed
noprefix also is about previous token
ldemailly
committed
Fix case where error is at start of line and fix illegal token case for prefix eg @
ldemailly
committed
who doesn't love linters changing under them
ldemailly
committed
correct comment about error logging in main
ldemailly
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.