Cross-Platform Path Separator Inconsistencies via path Package

[aniket866]

ISSUE

In pkg/config/localconfig.go, configuration directory pathing and creation utilities use the path package instead of path/filepath. The Go standard library path package is strictly designed for forward-slash URL paths and does not handle Windows backslashes (\).

Impact

On Windows systems, paths are constructed in a mixed format (e.g. C:\Users\Name/.config/microcks/config), which causes file system APIs and permissions logic to fail or look in wrong locations.

Code Reference

• pkg/config/localconfig.go

Issue visualization

graph TD
    A["getHomeDir() on Windows -> 'C:\\Users\\Name'"] --> B["path.Join(homeDir, '.config', 'microcks')"]
    B --> C["Result: 'C:\\Users\\Name/.config/microcks'"]
    C --> D["os.MkdirAll() creates folders with mixed slashes, breaking standard Windows paths"]

Loading

Steps to Reproduce

1. Execute any command that reads or writes config on Windows (e.g., microcks login).
2. The config directory is created/resolved in a non-native path format with mixed slashes.

---

Closes #476

[Vaishnav88sk]

Good catch. path/filepath is the right choice for OS-level paths. Please also add a test covering Windows-style home dirs if possible.

[aniket866]

hi @Vaishnav88sk I have done the requested changes , Please review

[Vaishnav88sk]

This overlaps with #442, so we should not merge both.

[Vaishnav88sk]

Also, the added test does not really verify Windows-style separator behavior yet. Because it builds the “Windows” home path using filepath.Join(...), it ends up using the separator of the OS running the test. On Linux/macOS runners, this would still produce a path that can pass even with the old implementation.

So I’d like the test adjusted to assert a real backslash-style home path, or otherwise be made explicitly Windows-targeted.

[Vaishnav88sk]

ALso add copyright block to the test file.

[Caesarsage]

Thank you @aniket866

This has been fixed by #442 — pkg/config/localconfig.go now uses path/filepath (filepath.Join) for all config path construction, so Windows paths come out native.

I believe this can be closed.