More pre-parsing instructions

Open
  • Is something wrong?
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

The payload names only the existing pre-parsing instructions ADDTOPATH, INCLUDE and ESCAPE, and no files. Start by finding where those three are handled in the grammar-file parser and how warnings are reported today. The proposed ENABLE_REDEFINED_WARNING and ENABLE_UNUSED_WARNING semantics are not specified, so agree on them with the maintainer before coding. Done means both instructions are parsed, documented and tested.

Written by the indexing model from the issue text.

Description

enhancement

What we currently have

Pre-parsing instructions allow to configure the parsing of a grammar file. However the only ones available for now are:

  • ADDTOPATH
  • INCLUDE
  • ESCAPE

Ideads for new instructions

We could also have new instructions like

  • ENABLE_REDEFINED_WARNING
  • ENABLE_UNUSED_WARNING
Dominant language
C#
Stars
0
Forks
0
Avg merge
3d 4h
Merged PRs (30d)
5

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Natvs/Nt.SyntaxParser

All issues in Natvs/Nt.SyntaxParser

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.