Hi,
I came across MR !714 [1] and issue #560 [2] and wanted to express
strong support for this feature.
I'm also working on integrating with HyperKitty's REST API, and
the lack of a machine-readable schema has been a significant
pain point. Right now, I have to read the source code to figure
out:
- What endpoints are available
- What request formats each endpoint expects
- What the response structure looks like
- Which fields are required vs optional
[image: image.png]
An OpenAPI schema would solve all of these issues and make
third-party integrations much easier to build and maintain.
The MR looks well-crafted: it adds zero backward compatibility
impact, all tests pass, and drf-spectacular is the officially
recommended tool for Django REST Framework.
I'd love to see this merged. Happy to help test if needed.
[1] https://gitlab.com/mailman/hyperkitty/-/merge_requests/714
[2] https://gitlab.com/mailman/hyperkitty/-/issues/560
Thanks,
TomNewChao
Hello,
I hope you’re doing well. I’ve opened Merge Requests for the Postorius
project and would really appreciate your review when you have time:
*Issue #323 – Hide Non-Member Lists*
Fixes the mailing list display in user profiles so only actual memberships
are shown.
MR: https://gitlab.com/mailman/postorius/-/merge_requests/1104
*Issue #377 – Web UI URLs in Templates*
Adds dynamic Web UI URL substitution in email templates to improve
navigation.
MR: https://gitlab.com/mailman/postorius/-/merge_requests/1112
Both MRs are currently passing all CI/CD checks.
Thank you for your time and guidance!
Best regards,
Lavanya
