prioritize new chapters rather than just edited ones.
should avoid batch-renaming drowning out new chapters, and existing items being re-sorted in the feed when they're edited.
documentation here: https://api.mangadex.org/docs/dates/
* [FeedMerge] fix: sort items by timestamp descending
* [FeedMerge] fix: fetch 10 most recent items
This fixes a bug where the bridge e.g. fetched 10 items from the first feed and then nothing from the rest
* Use ActivityPub outbox for Mastodon (et al.) feed
closes#2754
* Better description for Mastodon bridge
I mean I could rename it to ActivityPub bridge if the maintainer so pleases
* [Mastodon] Please the lint
* [Mastodon] address feedback
* [Mastodon] fix link, address spelling case bug
* refactor
* [Mastodon] add username cache, fix try-catch, rename
* [Mastodon] shorten description to satisfy the lint
* [Mastodon] address feedback
* [Mastodon] support Secure Mode instances
* [Mastodon] add config documentation
* [Mastodon] update docs
Co-authored-by: Dag <me@dvikan.no>
the date handling
The deal posting date logic was wrong, and leaded to warnings and
notice. Now, only the feed with the deal sorted by date contains date
(the feed sorted by hottest deal does not contain a date anymore,
because there are no deal date in this case).
With UTF-8 byte-order mark in the file, the `ListActionTest::testOutput`
would fail after converting tests to PSR-4 namespaces:
invalid JSON output: Syntax error
Failed asserting that null is not null.
This is because ListAction::execute tries to create the bridge objects
and, when the files containing the bridge classes are not loaded yet,
the autoloader starts including them. Since this happens after output
buffering has begun, any text in the PHP file before the `<?php` tag
such as the BOM will end up in the buffer to be parsed by `json_decode`.
Previously, it worked by chance thanks to some other test including the file
before `ListActionTest`. With the restructuring, `Actions\ListActionTest`
will run sooner and become responsible for triggering the autoloader.
To prevent this in the future, I also disallowed BOM in the coding style.
The /all url now actually points to a specific item.
I think we want the frontpage for this.
Fixes:
Fatal error: Uncaught Error: Call to a member function find() on null in NotAlwaysBridge.php:37
* [GitlabIssueBridge] new bridge
This tracks issue comments on arbitrary gitlab projects.
* [GitlabIssueBridge] Prepare for Merge Request support + fixes
- Proper UIDs
- Default bridge name fixed
- Fix cache identifiers
- Add TODOs
* [GitlabIssueBridge] creation timestamp preferred
And prefer original author over editor.
* [GitlabIssueBridge] Do not add date to item title
Prettier without it.
* [GitlabIssueBridge] Support Merge Requests
This bridge can now generate feeds for Merge Requests.
* [GitlabIssueBridge] typo
* [GitlabIssueBridge] Fix Img src attr in comments
* [GitlabIssueBridge] Fix function call
* [GitlabIssueBridge] Fix test
Use gitlab.com if no h parameter was given.
Fixes a phpunit test.
* [GitlabIssueBridge] linting
* [GitlabIssueBridge] Add MR support to description
* [GitlabIssueBridge] Move function collectData
* [GitlabIssueBridge] rm single-use class constants
* [GitlabIssueBridge] Remove manual caching
Just depend on rss-bridges built-in caching.
