feat(transformer-compile-class): add hashExplicitName option, workaround #2366 #3173
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.
Summary
This PR added a
hashExplicitName
to workaround the duplicated class error in #2866.Details
#3168 fixes the hmr problem for hashed class names, but when users are using a meaningful compiled class name like
:uno-my-class:
, it will throw an error since theuno-my-class
is already in shortcuts.Compared to customizing both
trigger
andclassPrefix
, it's easier for users to simply addhashExplicitName: true
in the options.