-
Bug
-
Resolution: Won't Fix
-
Low
-
Minor
-
Under some situations, it is needed to use the v1 Get Content API with ?expand to get pages with its author and restrictions.
In contrast, v2 Get Page API only provide authorId as of today.
V2 API don't support ?expand. However, in order to still retrieve Page Restriction and full Author information (e.g. "publicName"), it is needed to use two v1 APIs respectively. Specifically, v1 Get User API and v1 Get Content Restriction by Operation API, which are not deprecated (yet) and have no v2 equivalent.
In order to migrate from v1 Get Content API to v2 Get Page API, the developer will need to integrate two more v1 APIs, which may be deprecated soon too. This is effectively a gap blocker for migration to v2.
Please consider deprecating v1 Get Page API only six months after v2 Get User API and v2 Get Content Restriction API are in place.