fix(actionCreators): Migrate mergeGroups to async/await and remove callbacks - #126252
Closed
sentry[bot] wants to merge 2 commits into
Closed
sentry[bot] wants to merge 2 commits into
sentry[bot] wants to merge 2 commits into
Conversation
…llbacks Co-authored-by: sentry[bot] <39604003+sentry[bot]@users.noreply.github.com>
Member
|
dupe of #126268 |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses the
no-callback-api-requestcoding convention violation instatic/app/actionCreators/group.tsxrelated to themergeGroupsfunction.Problem:
The
mergeGroupsfunction was partially migrated to useapi.requestPromisewithasync/await, but it still accepted and invokedoptions.success,options.error, andoptions.completecallbacks. This hybrid approach violated the coding convention which mandates promise-based error handling over callback patterns.Solution:
static/app/actionCreators/group.tsx(mergeGroups):options: RequestCallbacksparameter.try/catch.static/app/views/issueList/actions/index.tsx(Call Site 1):{}third argument passed tomergeGroups..catch(() => {})to themergeGroupscall to prevent unhandled promise rejections for this fire-and-forget usage.static/app/views/issueDetails/groupSimilarIssues/similarStackTrace/index.tsx(Call Site 2):new Promise((resolve, reject) => { mergeGroups(..., {success, error}) })wrapper with a directmergeGroups(api, {...})call, leveraging the function's new promise-returning nature.Note: The
RequestCallbacksimport instatic/app/actionCreators/group.tsxhas been retained asbulkDeleteandbulkUpdatestill utilize this callback pattern and will require separate migrations.Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Fixes CODING-CONVENTIONS-4KZ
@sentry <feedback>: Autofix iterates on these changes@sentry stop iterating: Autofix stops iterating on this run