Windows Command - need to use the backward Slash - #23197

LGTM.

Note:
Let me use this opportunity to mention that nowadays, modern Windows systems can handle forward slashes on the system level (i.e. file explorer) and even on the command-line interpreter level (depends on which one you use). If we consider just the built-in ones, in PowerShell you are safe to use the forward slashes:

Whereas the older Command Prompt can't handle this. It's up to users in the end, which interpreter they use. The fact is that PowerShell is also available in the Microsoft's minimal container images.

The reason I'm mentioning it are the recent discussions about Windows platform improvements and I consider this as an opportunity for an improvement.
When it comes to the documentation, to make it slash agnostic, we can be more specific about the interpreter used in the examples (and eventually end up with a single example for each case regardless of the platform, a bit cleaner docs for free).
When it comes to the distribution, we already know that we need to do something about PicoCLI, which is the common source of this type of issues on the Keycloak end.

Passing run #8937 ↗︎

0

527

48

0

0

Details:

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}