-
Notifications
You must be signed in to change notification settings - Fork 935
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
unable to re-export after deleting the components from the remote #2341
Labels
Comments
I am not sure I follow:
|
davidfirst
added a commit
that referenced
this issue
Feb 13, 2020
…sed and vice versa, to enable re-exporting a component after deleting it
davidfirst
added a commit
that referenced
this issue
Feb 14, 2020
…sed and vice versa, to enable re-exporting a component after deleting it (#2345)
Thanks @Tallyb . |
davidfirst
added a commit
that referenced
this issue
Feb 17, 2020
* fix #2211 and #2308, when exporting to multiple scopes, make sure to not export their dependencies when these dependencies themselves are not export pending (#2309) * bump dev version * resolve #2268, prevent logger from holding the terminal once a command is completed by adding an error handler. Also, changed some "logger.debug" to "logger.silly". Also, support configuring the logger level by running "bit config set log_level <level>". Also, limit the number of concurrent files write to 100 (#2310) * fix typo in the BitId README * fix "bit status" and "bit tag" when new components require each other by module paths (#2313) * Fix e2e-tests to avoid code execution inside "describe" blocks (#2329) * move all Helper instantiation from describe to before. * fix defaultScope tests, remove code that was entered by mistake in the describe block to before block. * delete javascript-hook.e2e file, the tests there were written long ago, marked as "skip" and not relevant anymore. * support import/require statements of module paths when it has no scope-name (e.g. "@bit/button") (#2331) * resolve part of #2341, enable "--all" flag when "--all-versions" is used and vice versa, to enable re-exporting a component after deleting it (#2345) * Fixed broken link leading to quick start guide (#2338) * fix dynamic dist reference from package.json (#1808) when isolating via capsule (#2348) * remove .only from extension tests Co-authored-by: Erik <arebokert@hotmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If I recreated my remote collection or removed my remote components but left them locally, then trying to re-export them, here is what happens:
bit export <my-remote>
=> returns "nothing to export".bit export <my-remote> <glob>
=> returns "nothing to export".bit export <my-remote> <id>
=> returns "component X has been already exported to Y".bit export <my-remote> <glob> --all
=> returns "error: component X was not found.".bit export <my-remote> <glob> --all --all-versions
=> succeeded!Steps to Reproduce
bit export <remote>
Expected Behavior
Currently, to bypass this issue, you have to run
bit export <remote> <component-id-or-glob> --all versions --all
.the
--all-versions
flag makes sure to export non-staged versions.the
--all
flag makes sure to export non-staged components.this is not trivial.
I suggest the following:
--all
, it'll enable--all-versions
flag.--all-versions
, it'll enable--all
flag.--all
to--include-non-staged
? Tallyb , itaymendel .--all
flag. Tallyb , itaymendelScreenshots, exceptions and logs
If applicable, add screenshots, exceptions, and logs to help explain your problem.
Specifications
The text was updated successfully, but these errors were encountered: