Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] viper doesn't support case sensitive keys #116

Closed
aetaric opened this issue Oct 25, 2024 · 1 comment
Closed

[BUG] viper doesn't support case sensitive keys #116

aetaric opened this issue Oct 25, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@aetaric
Copy link
Owner

aetaric commented Oct 25, 2024

Describe the bug
When working with path mappings in arr services, viper is forcing the key case to lowercase, violating the YAML spec. This is causing issues with checkrr being unable to find the files in arr services.

To Reproduce
Steps to reproduce the behavior:

  1. set an arr service's path mapping to have capital letters in the path.
  2. run checkrr with the config and the --debug flag
  3. observe checkrr reading the path mapping key as a lowercase value in the debug output.

Expected behavior
Map key case should be respected.

Screenshots
n/a

Desktop (please complete the following information):

  • OS: all
  • Browser: all
  • checkrr Version: >=3.1

Additional context
See spf13/viper#373 and spf13/viper#1014

@aetaric aetaric added the bug Something isn't working label Oct 25, 2024
@aetaric aetaric added this to the 3.5.0 milestone Oct 25, 2024
@aetaric aetaric pinned this issue Oct 25, 2024
aetaric pushed a commit that referenced this issue Oct 25, 2024
Things might be slightly broken.
@aetaric
Copy link
Owner Author

aetaric commented Oct 25, 2024

If you are having issues when using the path mapping directive for arr services, this is why. It will be patched in 3.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant