Skip to content

Add Legacy Comparison Flag #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 42 commits into
base: parse-cabal-project-parsec
Choose a base branch
from

Conversation

jgotoh
Copy link
Owner

@jgotoh jgotoh commented Jan 24, 2025

Please read Github PR Conventions and then fill in one of these two templates.


Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:


Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

jgotoh added 12 commits January 10, 2025 22:40
Expects Invalid subsection warning by the Parsec ProjectConfig parser.
Currently the warning is issued twice:
First warning: "Warning: <ROOT>/else.project, else.project: Unrecognized
section '_' on line 3" is issued by the legacy parser,
Second warning: "Warning: dir-else/else.config:3:5: Invalid subsection
"_"" by Parsec Parser.
When we remove executing the legacy parser, we can remove the duplicate warning.
@jgotoh jgotoh force-pushed the add-legacy-comparison-flag branch from adf676b to 2c593ca Compare January 24, 2025 13:36
@jgotoh jgotoh force-pushed the parse-cabal-project-parsec branch from eededa4 to 8e08b0c Compare February 24, 2025 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant