To reduce clutter in a user's workspace, and to reduce the amount of boilerplate, being able to produce the data file in the .jewl directory would be a nice streamline of passing the data from jewl-go to Jewl.jl
Jewl.jl could also update it's API to use GetProject instead of Load so that it checks for a .jewl directory, and gets whatever project is in there. This would require some more changes on Jewl.jl's end but this could help reduce clutter and boilerplate for users.
To reduce clutter in a user's workspace, and to reduce the amount of boilerplate, being able to produce the data file in the .jewl directory would be a nice streamline of passing the data from jewl-go to Jewl.jl
Jewl.jl could also update it's API to use
GetProjectinstead ofLoadso that it checks for a.jewldirectory, and gets whatever project is in there. This would require some more changes on Jewl.jl's end but this could help reduce clutter and boilerplate for users.