Name custom in the BACKUP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
The current problem is in the Backup tab: when creating a new backup process, it is not possible to enter a name for the resulting file. As it works today, the file is generated with an unfriendly, hard-to-read name.
Describe the solution you'd like
A possible solution would be to add an optional field where the user can define a custom name for the backup file.
Describe alternatives you've considered
A possible solution would be to add an optional field where the user can define a custom name for the backup file.
Additional context
No response
Will you send a PR to implement it?
Yes
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
No files or tests are named. Start by locating the Backup tab and the flow that creates a new backup process, then trace how the resulting filename is generated. Done means an optional user-provided name is accepted and the backup file uses it while retaining the existing behavior when no name is entered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100