Add standalone Dream Maker structural linter - #335
Open
scroogemcduck1068 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
About The Pull Request
Closes #279.
Adds a dependency-free Python linter that recursively discovers every code/**/*.dm file without invoking DreamMaker. It emits stable path:line:column diagnostics or structured JSON and returns nonzero for validation errors.
Implementation walkthrough
This intentionally does not claim compiler equivalence. Rules are conservative and modular: unsupported context-sensitive DM semantics remain DreamMaker's responsibility instead of generating speculative diagnostics.
Verification
Why It's Good For The Game
DM contributors currently need compiler-oriented feedback even for simple structural mistakes. A fast standalone check catches malformed strings/comments, delimiters, and preprocessor structure with actionable locations before a full build. That shortens feedback loops locally and in CI while the conservative scope avoids pretending to replace DreamMaker. The implementation is documented and easy to extend as the project identifies additional low-false-positive rules.