Bit's Gitter channel. Feel free to ask anything, help others and have fun. https://bit.dev
@molnarzs , I just merged a fix for this into master.
teambit/bit#1921
With this fix, it doesn't run the Angular compiler to parse the entire project, so all these errors should be gone.
We're going to release a new version very soon.
teambit/bit#1921
With this fix, it doesn't run the Angular compiler to parse the entire project, so all these errors should be gone.
We're going to release a new version very soon.
hi @moreno-nt you can add several files to the same component in a single command (or an entire directory). additionally you can track many components with a single command.
right now the way to do it is by pre-tracking the components before ci, and commit it... so the CI will be the one running the
right now the way to do it is by pre-tracking the components before ci, and commit it... so the CI will be the one running the
tag command.
Bit does not know how to model the components for you. understanding if a file should be a part of the component - or be a part of another component is not a simple task.
we have build an internal service that can do just that, but this is not GA at the moment.
if you mean that you want a CI that automatically understand if there are new components and can isolate them perfectly automatically - no. sadly this is not available.
however, if you simply run
however, if you simply run
bit add and isolate the new components, and commit the changes to git, you can have bit tag and export the components.
if no new components/files where added, Bit will be ablet o export all modified components
we are working on a service to resolve it, but it'll take a while. requires a lot of statistics to properly understand how to properly isolate components in many use cases
well the thing is when it's a new component we made it work by doing bit add src/components/ for example, then it adds the new but it tracks everything as components even new files. It would be good to have a bit add files for example which check which is the closest main file and attach the files to it
I understand yes
here's an example project
https://github.com/GiladShoham/bit-add-many-example
https://github.com/GiladShoham/bit-add-many-example
if you have a specific convention you use, and all components support it - it should work.
Ok, so if we have the same structure accross our repo, let's say all main files are src/components/main.tsx and dependencies src/components/static/ , when we add a new file into static we can automatically do it with this bit SDK without doing manually bit add filename --id component ?
Just checking cause there is no clear documentation in this sdk
and thanks btw :)
the SDK is not well documented... but you can do that.
it gives you APIs to the
in your case, if you have a specific convention, you can build a tree of components from that convention during CI, and push it to the
it gives you APIs to the
bit add command. So you can use JavsScript code to create the components.in your case, if you have a specific convention, you can build a tree of components from that convention during CI, and push it to the
bit.addMany command.
if any of the components you are trying to add is already tracked by Bit - it will be discarded.
so only new components and dependencies will be added.
https://github.com/GiladShoham/bit-add-many-example/blob/master/addMany.js
this file builds the components from the very specific file tree
this file builds the components from the very specific file tree
there's not much Bit code in there.... but if you have specific questions about the API, please open a github issue so the answers will be well documented.
Hi @moreno-nt
You might find this issue relevant for you:
teambit/bit#1945
It's another user doing the same as you.
He wrote some scripts to automate the process.
You might find this issue relevant for you:
teambit/bit#1945
It's another user doing the same as you.
He wrote some scripts to automate the process.
Also, if you need more help with the addMany API, let me know.
ok actually I guess we'll have to go with the addMany and configure it our own way
Well not sure where to start with the script yet
We appreciate your responsiveness in our team :)
We will try to use the addMany script, I'll ping you if we encounter issues
so I guess there should be a "handleDep" function ?
or you mean it does thanks to addMany ?
and sorry when I mean dependency I mean any new files in the compenent (not another component import)
I guess the part that's unclear to me is how to authenticate and get access to private collection from the Heroku build step.
Check this blog post
Sry, full link