Add UTC and Unix Epoch Filename decoration
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
The issue does not name files or tests. Start by reading the existing output-filename pattern setting and its help text, then trace how recording start times are used to form filenames. Done means users can select Unix Epoch, UTC, or timezone-included date/time decoration and the available pattern options are explained in the help text.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Add configurable behavior to the app which allows the user to select Unix Epoch, UTC, or TimeZone included decoration to the output filename of the recording indicating the start date and time of the recording.
Why do you want this feature?
Presently the filenames appear to be defaulting to local date and time of the device with no TimeZone included which is poor for records keeping and event matching.
Additional information
Presently the app allows you to specify a pattern for the output filename but does not include the components for UTC or epoch at the very least in the help box to indicate they are possible.
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 98
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Voice-Recorder
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Voice-Recorder#419 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FossifyOrg/Voice-Recorder#411 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
FossifyOrg/Voice-Recorder#441 ·
Maintainers usually reply within 1 day
-
toggle recording via bluetooth remote controlMay be free again A pull request for this issue was closed without being merged. Openfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Voice-Recorder#436 ·
Maintainers usually reply within 1 day
-
Audio LayeringOpenfeature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 18/100
FossifyOrg/Voice-Recorder#432 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Voice-Recorder
Similar issues
-
LiquidGlass / LiquidGlassContainer (iOS): padded content measured at the outer width and overflows by the paddingPossibly taken @aleclarson claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NativeScript/NativeScript#11561 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
navikt/mock-oauth2-server#1129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
thunderbird/thunderbird-android#11778 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
software-mansion/enriched-markdown#1042 ·
Maintainers usually reply within 2 days