parse <template> in "vue" files
#148
Open
+75
−8
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
didoda
changed the title
<template> in "vue" files<template> in "vue" files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi! thanks for the awesome work you have done with
ttag-cli! I am enjoying it in projects that usevuejs.I opened this PR with the intention to provide an enhancement in
vuefiles parsing: the parse of<template>in.vuefiles (as suggested in ttag-org/ttag#201).Known issue: the extracted line numbers of the
<template>part will be messed up; the reason: we put<template>extracted string after<script>extracted string, and pass it tobabel.transformSync... babel function won't consider js code if it's not afterimport { t } from "ttag".Bonus: github workflow that launches tests.