Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat!: implement rfc#136 (oauth, token refresh) #142

Merged
merged 15 commits into from
May 13, 2023

Conversation

ranseur92
Copy link
Contributor

@ranseur92 ranseur92 commented Apr 27, 2023

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Modification to auto-fetch may change intended behaviour

Description

Resolves:
#136
#131

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes (if not applicable, please state why)

Copy link
Owner

@Intevel Intevel left a comment

Choose a reason for hiding this comment

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

Thank you, just a few changes. And where is the Breaking Change? I can't see the commit?

package.json Outdated Show resolved Hide resolved
src/module.ts Outdated Show resolved Hide resolved
src/runtime/composables/useDirectusAuth.ts Outdated Show resolved Hide resolved
@Intevel Intevel changed the title Rfc/136 feat!: implement rfc#136 (oauth, token refresh) Apr 28, 2023
@ranseur92
Copy link
Contributor Author

The breaking change was "Modification to auto-fetch may change intended behaviour" I wasn't sure how the initial one worked, as it only seemed to fetch when the plugin was registered?

src/runtime/plugin.ts Outdated Show resolved Hide resolved
src/module.ts Show resolved Hide resolved
@Intevel Intevel merged commit d9e42d1 into Intevel:main May 13, 2023
5 checks passed
@Intevel
Copy link
Owner

Intevel commented May 13, 2023

Thanks for this PR, I will release this changes when we documented it and fixed other bugs.

@Intevel
Copy link
Owner

Intevel commented Jun 7, 2023

This PR is now released, but we have to document this changes.

@casualmatt
Copy link
Collaborator

I will do it if for you is ok

@Intevel
Copy link
Owner

Intevel commented Jun 7, 2023

I will do it if for you is ok

Sure, you can make an own branch and a PR for that.

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.

None yet

5 participants