Also processes markup in transpile. #119
Merged
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
Like how the Svelte compiler works, we should first process the markup, before we can process the script and style, to make sure we get a representative result.
|
Thanks! |
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.
Like how the Svelte compiler works, we should first process the markup,
before we can process the script and style, to make sure we get a
representative result.
This fixes an issue where the TypeScript preprocessor needs to look at
the markup to update the code
(see this PR: sveltejs/svelte-preprocess#155).
Since the mentioned PR is not merged yet, I did not create an issue, but
I think the language server should expose the same behavior as the
Svelte compiler.