Skip to content

feat: add ntn-compatible API parity command - #118

Closed
rossbrg wants to merge 2 commits into
Coastal-Programs:mainfrom
rossbrg:feature/ntn-api-parity
Closed

feat: add ntn-compatible API parity command#118
rossbrg wants to merge 2 commits into
Coastal-Programs:mainfrom
rossbrg:feature/ntn-api-parity

Conversation

@rossbrg

@rossbrg rossbrg commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add an api <path> command with ntn-compatible inline body, query, header, stdin, JSON, multipart, method, and raw-response handling
  • add compatibility aliases for login/logout, data sources, pages, and files
  • add Notion token/version environment aliases plus per-request --notion-version
  • embed an API endpoint catalog with ls, --spec, and --docs introspection
  • document the new command and compatibility surface

Upstream sync

Rebased onto upstream main at e76dfa3. This deliberately leaves behind the fork commits already incorporated upstream by #90 and #107. Conflict resolution preserved the current workspace OAuth token masking and placed the API-parity entries under Unreleased.

Verification

  • make fmt
  • make test
  • make build
  • make lint
  • live read-only ./build/notion-cli --auth-workspace haven api users/me --json
  • ./build/notion-cli api ls --json

@rossbrg

rossbrg commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

Closing this in favor of Notion's first-party ntn CLI. A current review found that the proposed parity surface now duplicates the actively maintained official CLI, while the static endpoint catalog is already stale and the raw absolute-URL path needs additional credential-safety work. My local workflows and workspace routing have been migrated to official ntn, so I no longer think this large compatibility layer should be merged.

@rossbrg rossbrg closed this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant