fix(element-plus): handling components without styles #468
Conversation
This file contains 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
sxzz
approved these changes
Jul 19, 2022
sxzz
changed the title
|
Maybe can add a noStylesComponent option for users to configure themselves. |
I think this would be handy for getting around such blocking cases quickly without having to wait for a new release of |
|
You are so efficient, it's amazing 👍 |
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.
Description
Element Plus can contain components without css files. There seems to be only one such component right now,
ElAutoResizer. Now it comes to an error of loading un-existed styles file.This PR adds a list of components without styles that can be updated later, and toggles the
importStyleflag to false for them.Linked Issues
element-plus/element-plus#7933