Describe the bug
The poly tool will not run in a directory that contains deps.edn unless workspace.edn is also present.
To Reproduce
Steps to reproduce the behavior:
create a brand new folder mkdir fresh
change into it cd fresh
run poly -- it works and starts a shell
exit the poly shell
create a minimal deps file echo {} > deps.edn
run poly -- it fails with Couldn't open 'workspace.edn': /path/to/fresh/workspace.edn (No such file or directory)
Expected behaviorpoly should start a shell even when deps.edn is present (and workspace.edn is not).
Versions (please complete the following information):
Poly: 0.2.19 and 0.2.20-SNAPSHOT
I believe this is due to some code left over from supporting the old project structure that uses the presence/absence of deps.edn to determine whether this is a new or old project -- it sees deps.edn, assumes it is a new project, and then fails to open workspace.edn
Describe the bug The
poly
tool will not run in a directory that containsdeps.edn
unlessworkspace.edn
is also present.To Reproduce Steps to reproduce the behavior:
mkdir fresh
cd fresh
poly
-- it works and starts a shellpoly
shellecho {} > deps.edn
poly
-- it fails withCouldn't open 'workspace.edn': /path/to/fresh/workspace.edn (No such file or directory)
Expected behavior
poly
should start a shell even whendeps.edn
is present (andworkspace.edn
is not).Versions (please complete the following information):
I believe this is due to some code left over from supporting the old project structure that uses the presence/absence of
deps.edn
to determine whether this is a new or old project -- it seesdeps.edn
, assumes it is a new project, and then fails to openworkspace.edn