[FEATURE REQUEST] s3/cont/consts.go
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 25
- Forks
- 103
- Avg merge
- 29m
- Merged PRs (30d)
- 2
Description
Why this feature?
// HashPath defines the storage path for hash data within the 'openim' directory.
hashPath = "openim/data/hash/"
// TempPath specifies the directory for temporary files in the 'openim' structure.
tempPath = "openim/temp/"
// DirectPath indicates the directory for direct uploads or access within the 'openim' structure.
DirectPath = "openim/direct"
Suggested Solution
这几个路径,是否可以作为配置?
Additional Information
No response
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
Start by reading s3/cont/consts.go and trace how hashPath, tempPath, and DirectPath are used. Determine the project’s existing configuration entry points, then make these three storage paths configurable and verify that their configured values are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100