Support tagging.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the linked File-Manager request and General-Discussion comment to understand the proposed tagging approach. The issue does not identify files, tests, or an implementation entry point; first clarify how tags should be stored and how combining and excluding them should work when filtering. Done would mean those behaviors and their scope are agreed, but the issue alone does not define them.
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 bug report will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
- I optionally donated to support the Fossify mission.
Feature description
A one-to-many correspondence, possible to combine and exclude when filtering.
Why do you want this feature?
To organize them in a manner which embeds into the audio file, or via the file system as https://github.com/FossifyOrg/File-Manager/issues/60#issue-2151476679 requests, but via the Notes GUI for the sake of accessibility to the technically less competent, and convenience for all, regardless of competence.
Additional information
https://github.com/FossifyOrg/General-Discussion/issues/127#issuecomment-1958772679
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
software-mansion/enriched-markdown#1033 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
app
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LawnchairLauncher/lawnicons#4180 ·
Maintainers usually reply within 1 day
-
Kotlin extra warnings in GeneratedAppGlideModuleImplPossibly taken @bacecek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 18 days