Skip to content

Conversation

SvenWesterlaken
Copy link
Contributor

@SvenWesterlaken SvenWesterlaken commented Sep 26, 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)

Description

As stated by my issue #350, allowing for a signal of the AbortController to be passed through would be beneficial. In this pull request, this is implemented. So this closes #350

This is only implemented for the find and findOne methods as the other methods might have bad side effects if cancelled by the signal.

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)

@nuxt-studio
Copy link

nuxt-studio bot commented Sep 26, 2023

Live Preview ready!

Name Edit Preview Latest Commit
Strapi Edit on Studio ↗︎ View Live Preview bce22ae

@benjamincanac benjamincanac changed the title Allow fetch options for find & findOne feat(find/findOne): allow options Nov 27, 2023
@benjamincanac benjamincanac changed the title feat(find/findOne): allow options feat(find/findOne): allow fetch options as third param Nov 27, 2023
@benjamincanac benjamincanac merged commit b360ad3 into nuxt-modules:dev Nov 27, 2023
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.

Allow cancellation of request by allowing the usage of an Abortcontroller and its signal in find and findOne methods
2 participants