CLI reports non-native default config path on Windows

Open Beginner friendly
#268 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start by tracing where the CLI constructs the ConfigPath value used in --help, focusing on the mixed separators shown in the issue. Reproduce with microcks --help on Windows and verify that the reported default path uses native Windows separators while runtime path behavior remains unchanged.

Written by the indexing model from the issue text.

Description

stale
Describe the bug

The CLI constructed the ConfigPath variable with mixed seperators and hence, the reported default config path in --help was wrong.

      --config string                 Path to Microcks config (default "C:\\Users\\HomePC/.config/microcks/config")

This seems to be a cosmetic issue only, the actual paths used by the runtime logic is different.

Expected behavior

The expected path should be C:\\Users\\HomePC\\.config\\microcks\\config on Windows

Actual behavior

Reports C:\Users\some_name/.config/microcks/config

How to Reproduce?

Run microcks --help on Windows

Microcks version or git rev

fde7e8febdbb48c30ca74ba51aa77e725f033105

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

source

Dominant language
Go
Stars
52
Forks
67
Avg merge
1d 1h
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microcks/microcks-cli

All issues in microcks/microcks-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.