-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): allow non-default-export client config file #1564
Conversation
Pull Request Test Coverage Report for Build 9211065904Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Better to check default export in node side instead of filtering it in client code.
- Better to add e2e tests for the changes.
I'm not pretty sure about the first one, So you mean importing this file on the node side and see if the default export is available? So what's the motivation of this? We can't just filter those files which does not have sport because we shall import them anyway to have their library and style file imported. Also, if the file is containing some style files import like css and scss, An error is expected at node side because we are not dealing them with bundlers. And I think there is no actual performance decrease for using a namespace import, Because only the default export is expected on this file. |
I mean to check the file content in node side or something. As I remember, v1 did similar thing by checking It could avoid the extra But yes it's nice to have but not such necessary. |
I think checking without ast may introduce fail positive, so I prefer the original one. I don't think ast check should be introduced here. |
A e2e test about config file with no export default is added. |
shit, why is windows failing (ー_ー)!! |
@@ -0,0 +1 @@ | |||
import './test.css' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should check if the styles are applied correctly to the target elements
do not require
export default {}
with client config fileuseful for: