-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Pinned posts do not appear in the collection's post list #824
Comments
Thanks for reporting this. Can you share a bit more about your use case, so I can understand why you might want pinned posts at that endpoint? Right now, it's designed to only provide a feed of posts. |
My use case was that I wanted to have a WriteFreely blog where the content is externally managed: as in, have a directory full of markdown files, which a script would sync to my WriteFreely instance, add them to the relevant collections, pin them if necessary, and so on. Part of this sync was deleting obsolete posts. I originally wanted to implement this by listing posts in the main collection (I only used one), but ran into this problem, that pinned posts weren't listed there, so I couldn't delete obsolete ones (I did not wish to keep track of post IDs already posted: everything that's not in the source repo should be considered obsolete, and to be deleted). I eventually switched to This particular case would be nicely supported if |
Describe the bug
When a post is pinned to a collection, it does not appear in the collection's post list.
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
/api/collections/{collection}/posts
endpoint..data.posts
.Expected behavior
Ideally, pinned posts would either be included in the listing by default, or a "pinned=true" query parameter or similar would let me ask WriteFreely to include them.
If this line in the source had its last argument as
true
instead offalse
, that'd solve my immediate problem.Application configuration
Version or last commit: 3e7d236
The text was updated successfully, but these errors were encountered: