Comments (3)
Yeah, fair enough.
Perhaps the demos folder should look like this:
demos/
src/
(demo source templates, config etc as now)registry/
(demo files built for the registry - HTML only)local/
(demo files built for local development - HTML, JS, CSS)
origami-build-tools demo
would be changed to generate both registry and local versions of the demos rather than only building one or the other.
Then it should be much clearer which files are used where, and it wouldn't really matter if the local files get committed, in fact it would save a developer an extra step in building them.
from origami-build-tools.
local versions of demos will contain large bundles of other components, and I don't really like those being committed. A change in file structure might be helpful though because it would enable a demos/local directory to be listed in .gitignore. Currently, targeting the same dir for build service and local demos does make it awkward to find the correct files to commit.
So, I suggest that normal demos continue to be saved in demos, and local versions are saved in a subfolder called local, which is also added to gitignore.
No real opinion on whether the tool should update configs automatically, but if it does, it would be good to make that clear in the CLI output so there's no magic. @kavanagh are you happy with this?
from origami-build-tools.
Yep
from origami-build-tools.
Related Issues (20)
- v11 bug: package.json.name validation is too lax
- Orphaned Repository - For Archiving.
- obt demo HOT 4
- remove `obt init` HOT 2
- add tests for the `dev` command
- Long lines get truncated in terminal
- proposal: add sub-command help flags
- Improve the karma-scrumple error message when dependencies have not been installed HOT 1
- Bug: obt test -- TypeError: Cannot read property 'trim' of undefined
- Defer to the depended on version of create-origami-component
- Use component `.remarkrc.js`
- Require component lint configuration HOT 4
- Is it ok that component configuration is dynamically required? HOT 1
- major: throw an error when `obt verify` finds readme issues? HOT 1
- feature: verify demo compilation per brand
- feature: install demo dev dependencies instead of using the build service HOT 1
- Feature request: Improve component spec v1 error messaging
- Feature: improve error message when origami.json.demos is not an array
- Feature: check the built demo html is syntactically valid HOT 1
- Bug: obt v11 beta uses wrong logic for validating origami.json version HOT 1
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 origami-build-tools.