Point to precise line in parsed source for parsing problems#10
Merged
Conversation
Collapse multiple replaced special chars to one "_" and add doctests.
Instead just alias to typing.Any. This should make it a bit easier to addopt docstub gradually.
avoids confusion with the parent classes `transform` method.
Otherwise, this fails on Windows which returns "file\\with\\..."
This makes it easier to test the class.
Also add a few tests for that class and remove the currently unused yields property.
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
1 participant
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.
When a grammar error occurs or an import for a doctype isn't known, point to the exact line of in the parsed sources.