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
you can see that the return value is not the expected one from the duct point of view.
We think that the #duct/include for profiles in the base config of the duct template, should point to existing files explicitly. For example dev.edn and local.edn. That means changing the following lines in the base config of the duct template:
The base
config.edn
declares two profile includes fordev
andlocal
.This is a problem for artifact names that start with either
dev
orlocal
.For example, if you include the following library to your project:
[dev.gethop/sql-utils "0.4.13"]
When duct starts reading the configuration it will throw the following exception:
We think the root of the problem is this line in the
core
library. Because if you run the following:you can see that the return value is not the expected one from the duct point of view.
We think that the
#duct/include
for profiles in the base config of the duct template, should point to existing files explicitly. For exampledev.edn
andlocal.edn
. That means changing the following lines in the base config of the duct template:What do you think? Is there are reason for having just
dev
andlocal
instead of specific file names and extensions?The text was updated successfully, but these errors were encountered: