Atlas "develop", add local paths to nim.cfg

[enthus1ast]

Atlas should have another option,
to just put local paths in the nim.cfg.

This way we could developing a module and use it directly in the consuming application.

For example it could be:

atlas develop /path/to/module 

This would then add the path to the module to the nim.cfg.
It could also add this to the nimble file?

[Araq]

What's the benefit over just adding the path yourself to nim.cfg?

[enthus1ast]

It could maybe also install dependencies, and also maybe add the module to the nimble file.
Then later when the module is done everything is ready to be released.

But yes, one can just add the path by hand, but for what we need tooling in general then.

[Araq]

/path/to/module might not have a corresponding URL yet so maybe it cannot be added to the Nimble file. I don't see why it would be useful. There is already atlas use dependency which serves a more useful use case.

[elcritch]

There is already atlas use dependency which serves a more useful use case.

More specifically if you pass a path to atlas use file://../dependency it'll use that path and try and find it's Nimble file. It should add it to nim.cfg.

Also you can setup a url.rules file that transforms the name to some path like is done in the integration tests.

Overall I also think atlas develop goes against Atlas's style of providing workspaces. For example, setup the Atlas workspace to be in a parent folder of both projects.

[elcritch]

😆 Though looks it adds requires "file://../mydep" to the local Nimble file. The nim.cfg works. I'll get a fix for the requires up.