Skip to content

fix: do not replace asana refresh token#37

Merged
d-klotz merged 1 commit intonextfrom
feat/improve-asana-api-module
Jun 4, 2025
Merged

fix: do not replace asana refresh token#37
d-klotz merged 1 commit intonextfrom
feat/improve-asana-api-module

Conversation

@d-klotz
Copy link
Contributor

@d-klotz d-klotz commented Jun 4, 2025

  • Asana only provides one long-lived refresh token, we should not replace it once we receive it.
  • Cleaned up code formatting for better readability and consistency.

- Updated `setTokens` method to handle refresh tokens correctly, ensuring only one long-lived refresh token is maintained.
- Enhanced expiration time calculations for access and refresh tokens.
- Cleaned up code formatting for better readability and consistency.
@d-klotz d-klotz requested a review from seanspeaks June 4, 2025 13:28
Copy link
Contributor

@seanspeaks seanspeaks left a comment

Choose a reason for hiding this comment

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

Yeah this works 👍

@d-klotz d-klotz merged commit f8d5c54 into next Jun 4, 2025
4 checks passed
@d-klotz d-klotz added the release label Jun 4, 2025
@seanspeaks
Copy link
Contributor

🚀 PR was released in @friggframework/api-module-asana@2.0.0-next.5 🚀

@seanspeaks seanspeaks added the prerelease This change is available in a prerelease. label Jun 4, 2025
@seanspeaks seanspeaks mentioned this pull request Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease This change is available in a prerelease. release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants