-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API] Missing Enclosure #1059
Comments
Using
I don't know golang but looking at the code I noticed this line in The |
Just stumbled upon the same issue. It's probably a perf optimization in order to avoid joins, but it would be really nice to have a way to include enclosures, probably as an optional arg or something. It's quite the opposite when it comes to feeds though. Here is how most offline-first clients with full-scale cache operate:
This approach allows two-way sync with reasonable number of HTTP requests and it also avoids querying the same data multiple times. Based on my experience with Miniflux so far, here is the current state of the API when it comes to this use case:
PS. I'm also not familiar with Go, but I'm ready to try if maintainers are busy of focused on something else |
I tried to add enclosures with something like this patch
and with python api it look fine, it started to return enclosures which look the same to ones returned by edit: |
@fguillot Sorry for pinging you… Is solution of mine acceptable to get enclosures when using |
Running official docker image version
2.0.28
Some feeds offer an "Attachment" / "Enclosure"
But the Json of the same article states it doesn't have any enclosures:
The text was updated successfully, but these errors were encountered: