![]() ![]() ![]() Even with submodules, they are read-only by default for exactly that reason.Īt any rate, what just mentioned is one of the reasons I am wary of having this type of multi-working path interface in a single instance/window: you have to handle integrations (like git), extensions, refactoring, debugging, etc, etc, etc. You wouldn't be able to reliably make changes to support one project without worrying about the change having consequences for other consumers down the road. If the modules are tightly coupled, then they really aren't isolated modules. ![]() This problem is what package managers are largely intended to solve. Sounds like a use case for submodules I'm not sure how your project would reference another, unless you were aliasing with some mechanism, such as npm linking, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |