refactor(api): remove namespace exports and use unique identifiers for API methods #238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors the API exports to remove all namespace exports and use unique identifiers for each API method. Previously, API routes were structured to match the REST endpoint hierarchy, with each endpoint exported as a namespace (e.g.,
pages.project.title.get()
). This allowed method chaining but caused several issues:pages.project.title.get()
) was rarely used in practice.Changes in this PR:
getPage
).api.ts
re-export these functions directly, without wrapping them in namespaces.BREAKING CHANGE:
Consumers must now import API methods as individual functions rather than accessing them via namespaces. This improves documentation compatibility and enables better tree-shaking for smaller bundles.