Skip to content

Conversation

wolveix
Copy link
Contributor

@wolveix wolveix commented Oct 1, 2025

Hello!

We rely on this library for various automations and internal tools, so the announcement of Data Sources from Notion concerned me (with regards to when it may be implemented here).

This is my first time working directly with Notion's API (outside of webhooks), so my apologies if anything seems odd! I ran through the upgrade guide and implemented all of the changes I could see.

Do note that I haven't added all tests for data sources yet.

This closes #195.

Copy link

@y-kawawa y-kawawa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wolveix Thanks for the PR! I’ve left a comment.


type DatabaseService interface {
Create(ctx context.Context, request *DatabaseCreateRequest) (*Database, error)
Query(context.Context, DatabaseID, *DatabaseQueryRequest) (*DatabaseQueryResponse, error)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this depends on the official Notion fix, removing it counts as a breaking change.
It might be a good idea to update the module path to v2, in line with semantic versioning.
Alternatively, if you’d prefer not to move to v2, another option could be to provide two notionVersions - 2022-06-28 and 2025-09-03 - and support both.
Of course, that would increase maintenance costs, so it also depends on the policy of this repository.

Copy link
Contributor Author

@wolveix wolveix Oct 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the comment! From reading Notion's release, it doesn't sound like they'll be supporting database querying at all moving forward (as I understood it, even querying with the old API version will outright fail with new databases).

I think moving to v2 makes the most sense. Though in saying that, I do believe this library has similarly had breaking changes in the past (the last commit in the repo).

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the response.
I also feel that moving to v2 would be a good option, but if this repository has followed a different approach in the past, it might be better to keep going that way.

Copy link

@y-kawawa y-kawawa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wolveix Additional comment.

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.

Do you have any plans to update API version from 2022-06-28 to 2025-09-03?
2 participants