feat(tags) Add minimal tag management to miniflux#4289
Open
pettijohn wants to merge 3 commits into
Open
Conversation
Extend PUT /v1/entries/{entryID} to accept an optional tags field
that replaces the entry tag list. Preserve existing title/content update
behavior and allow an empty tag list to clear tags.
Update the Go client request type and API examples.
Add a hidden /tags page that lists all tags with entry and unread counts. Reuse the category list item template for categories and tags, and add a tag-specific mark-all-as-read action. Add AI translations for new keys, alert.no_tag and page.tags.title.
pettijohn
changed the title
pettijohn
changed the title
|
Making search work with tags via api ( I know about opionated nature of this project, but having tags and not using them in api is strange. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Have you followed these guidelines?
auto make runto verify that /tags and /categories workThis pull request allows mutating entry
tagsthrough the API (currently only title & content may be mutated) and viewing them from/tags(refactored/categoriesto a shared item_list control).About 2.5 years ago I submitted feature request #2245 for adding upvote/downvote buttons to train AI on news that I care (or do not care) about. I understand that you closed it because it does not fit with the philosophy of miniflux. The idea of this PR is that an external service or reader client or greasmonkey script can interact with miniflux, saving metadata as tags. This keeps miniflux as a central feed repository, and any AI/LLM client has a way to interact with the storage model. No changes to the database, so no migrations required. No bloat of miniflux features.
Code Summary
This PR adds tag management support in two places:
PUT /v1/entries/{entryID}so API clients can replace an entry’s tags with an optionaltagsfield./tagsUI page that lists all tags, reusing the category list layout and supporting tag-specific “mark all as read” actions.Details
The API update keeps existing title/content behavior intact while allowing:
tags: leave tags unchanged"tags": []: clear tags"tags": ["foo", "bar"]: replace tagsThe UI update adds a read-only tag listing page at
/tags, with entry counts, unread counts, links to each tag’s entries, and localized labels. It does not add a top-level navigation item.