Expected Behavior

The diagrams should be color-blind safe.

For instance, the diagrams should use shapes hashed fill styles or diagram layers to distinguish "declaring dependencies", "internal configurations", "external configurations".

For instance, what do you think if the diagram is represented as follows? (plus the arrows between items)

LAYER: dependency declaration: api, c

Remove all additional resolvers from build.sbt, at least for releases, because artifacts published to Maven central repository should not contain additional repositories, and in fact don't need them because all dependencies are already in Maven central repo.

right now the image-loader middleware only supports the formats ICO, JPEG, PNG, GIF, SVG and WEBP.

It would be very useful to also add the new AVIF format, that is already being used on the web and that is quickly gaining popularity and browser supports

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

Or a new flag should be introduced (e.g. task --names) to just output the names of available tasks, with no descriptions.

Currently, a Taskfile with no descriptions returns:

$ task -l
task: No tasks with description available

While the solution is fairly intuitive (i.e. add a description to every task), the behaviour is surprising. Not to mention it would make the completions

In the same way that we can do:

DotNetCoreBuild
DotNetCorePublish
etc

Would be good to be able to run DotNetCoreWatch as a top level task in my Cake Build script.

This issue is tracking the documentation that has to be updated.

• Document new platform commands
• Update the section dedicated to page <title> and tell about [Browser.documen

We're moving in the direction of Pants no longer registering all of its plugins by default and instead requiring users to opt-in. For example, you must explicitly opt in to pants.backend.python.lint.isort in V2, whereas V1 has pants.backend.python activated by default.

However, there is no good way to discover the possible backends outside of looking at the source code for this project.

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b