-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reduce code or complexity #853
Comments
Some examples.
|
I'll work on this. |
We agreed on day.js now: #887 |
Also related I'd say: snapshot-labs/snapshot-plugins#20 (comment) |
About this, I'm guessing you mean this. Below is my environment. package.json
vite.config.ts
What do you think? |
I've just tested the latest version of @vitejs/plugin-vue and @vue/compiler-sfc. package.json
Two problems I mentioned in the last comment were still alive, so I think $ref and $computed will be of limited use and for the purpose of keeping code clean and consistent I'm not sure they are helpful right now, if my take is right. |
@bonustrack @mktcode About this, it seems to me that moving only plugin components to snapshot-plugins means lots of adding, changing of import because it's outside of the path unplugin-vue-components looking at, but is it good? |
Moving the UI components would be part of a more comprehensive refactoring of the plugin mechanic and should be handled in its own issue imho. (Adjusting the snapshot-labs/snapshot-plugins#20 (comment) is for now just a minimum approach to solve #666 but maybe also kind of a first step in such a refactoring. Just mentioned it as a potential example but maybe the scope of this issue needs to be narrowed down a bit more. Currently it's a bit "infinite". |
I'll just make PRs I've done for now Ready for review. |
This is supposed to be a placeholder for documenting all the ideas for refactoring. There will be separate issues created in due time. Locking this thread. |
Reduce code, remove code duplicate, simplify things, remove unused dependency, if you can reduce code or complexity without removing a feature, feel free to make a PR.
The text was updated successfully, but these errors were encountered: