You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to import code like import_code('~/some/path') with a symbol like ~ or using / in the first character to get the root path of the project so I don't have to be looking backwards with double dots, also it would be great if it could be configured like using ~ for root path and @ to import from, for example, a vendor folder.
The text was updated successfully, but these errors were encountered:
Okay I've looked into this. The issue is that with how greybel is designed right now it has no way of knowing what the root directory should be. I mean I could always take the current pwd environment variable as the root but I think this will properly lead to confusion.
To add this feature I would probably need to add some kind of root configuration file. Something like in node where you have a package.json.
Anyway this may take some time to implement since I need to decide on a good structure for the configuration file and I also need to add some kind of init command to greybel to create some basic configuration file for the user. It is still a good suggestion though.
It would be great to be able to import code like import_code('~/some/path') with a symbol like ~ or using / in the first character to get the root path of the project so I don't have to be looking backwards with double dots, also it would be great if it could be configured like using ~ for root path and @ to import from, for example, a vendor folder.
The text was updated successfully, but these errors were encountered: