Support saved configuration for `tyger buffer` commands
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 74
- Forks
- 23
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 7
Description
Save values for --block-size and --dop in a file in $XDG_CONFIG_HOME. These values, if present, would become the default.
We could also support different values per hostname:
{
"myeastusaccount.blob.core.windows.net": {
"read": {
"dop": 32
},
"write": {
"dop": 64",
"blockSize": "16MiB"
}
},
"mywestusaccount.blob.core.windows.net": {
"dop": 512
"blockSize": "4MiB"
},
"*": {
"dop": 32
"blockSize": "16MiB"
}
}
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the tyger buffer command implementation and its handling of --block-size and --dop; done means those values can be loaded from $XDG_CONFIG_HOME, with hostname- and operation-specific defaults if that optional configuration is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100