ApiLink always resolves to /reference/<...> regardless of the active Docusaurus version. For the next version, it should resolve to /reference/next/<...>.
This causes the docs CI check to fail when a PR introduces new public classes, since they don't exist in the stable API docs yet.
Parity tracking for apify/crawlee-python#1867 and apify/apify-client-python#780.
Note - the right way to go about this is likely moving ApiLink to a shared theme. Currently, there are small differences between the ApiLink implementations in the projects, though, so it's not straightforward.
ApiLinkalways resolves to/reference/<...>regardless of the active Docusaurus version. For the next version, it should resolve to/reference/next/<...>.This causes the docs CI check to fail when a PR introduces new public classes, since they don't exist in the stable API docs yet.
Parity tracking for apify/crawlee-python#1867 and apify/apify-client-python#780.
Note - the right way to go about this is likely moving
ApiLinkto a shared theme. Currently, there are small differences between theApiLinkimplementations in the projects, though, so it's not straightforward.