Comments (6)
Our CI tools use these commands, so they'll still need to be accessible somehow.
When installing the dependencies of the project, it will have access to the CLI.
However some could create a cozy-cli on his/her own and see if it responds to the 3 U : useful, usable and used. Maintain another project sounds we become a labyrinthine system.
I think it is good way to move forward indeed. Thanks for you answers !
from cozy-template.
There is a fair amount of logic in the package.json
and this logic has to be duplicated across projects. When we want to make a change (adding hot-reload for example), it is difficult to do this across every app in 1 go.
Since cozy
is meant to be a platform where developers would build apps, it would be good if evolution in developer tools could be easy to share. This is why I was thinking that a dedicated tool could be in a separate repository. It would initially contain the commands listed in the package.json (see above) so that we can do cozy run
, cozy build
etc...
Then if we make an improvement, the developer could just do yarn update cozy-cli
and be good to go.
from cozy-template.
I suggest cozy-template
is the source of truth for scripts and configurations, and whenever you want to use something in your own project, you copy/paste from cozy-template
.
However some could create a cozy-cli
on his/her own and see if it responds to the 3 U : useful, usable and used. Maintain another project sounds we become a labyrinthine system.
from cozy-template.
Not sure I understand the need, honestly.
from cozy-template.
Not sure really that it's gonna make things a lot easier but I suppose this should be discussed with everyone also.
from cozy-template.
Here are the downsides I see:
- Our CI tools use these commands, so they'll still need to be accessible somehow.
- The logic in the command is strongly coupled with the repo's set-up (mostly the webpack configuration), so keeping them in the same place is actually a good thing. It also allows for flexibility of it's needed.
They aren't major downsides, but I don't feel like the upsides are major either. We rarely have critical things to change in these commands so it can just be done over time or on friday afternoons.
from cozy-template.
Related Issues (7)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cozy-template.