Skip to content

Conversation

scottlovegrove
Copy link
Contributor

This adds a new, optional, API surface that allows the consumer to dictate whether they want to access the staging APIs. By default, if not present, it will revert to the production API. Getting staging data is fully opt-in.

@scottlovegrove scottlovegrove self-assigned this Sep 1, 2022
@scottlovegrove scottlovegrove requested review from a team, proxi and pawelgrimm and removed request for a team September 1, 2022 11:36
Copy link
Contributor

@pawelgrimm pawelgrimm left a comment

Choose a reason for hiding this comment

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

I didn't have time to do any smoke testings, but the code changes seem good 👍 I left some non-blocking comments for your consideration, but I don't need to see this again.

@scottlovegrove scottlovegrove changed the title chore: Adds support for accessing staging data @scottlovegrove chore: Adds support for accessing Todoist via a baseUrl Sep 5, 2022
@scottlovegrove scottlovegrove changed the title @scottlovegrove chore: Adds support for accessing Todoist via a baseUrl chore: Adds support for accessing Todoist via a baseUrl Sep 5, 2022
@scottlovegrove scottlovegrove merged commit 31a35c5 into main Sep 7, 2022
@scottlovegrove scottlovegrove deleted the scottl/add-staging branch September 7, 2022 13:06
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.

3 participants