Verify case-sensitivity behavior in `rstudio-connect` chart
Open
Nobody has claimed this yet.
team: connect
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
We have a handful of dynamically-set default settings that are case sensitive. What happens if a user sets these settings as well (with different casing)?
- last in wins, deterministic on some ordering? Alpha?
- last in wins, non-deterministic?
Also, we should document whatever we find
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the rstudio-connect chart and identify the dynamically set default settings that are case sensitive. Reproduce user overrides with different casing, determine whether precedence is deterministic, and document the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100