Skip to content

Conversation

@Numpsy
Copy link
Contributor

@Numpsy Numpsy commented Sep 11, 2024

Description

Referencing the comments in #2820, and assuming that the return type is actually wrong, I think it should be awating the PullRequest.Create so that it gets awaited inside the retry machinery?

Still a draft, as if it's a correct cfhange it needs release notes (and It'd be a breaking change to the public API)

@xperiandri
Copy link
Collaborator

Indeed, that would be strange

@Numpsy
Copy link
Contributor Author

Numpsy commented Sep 20, 2024

Given that this is a breaking API change, would it need to be held for the .NET 8 update release?

@xperiandri
Copy link
Collaborator

That would be more appropriate.
However 7.0 can be released if urgently needed

@Numpsy
Copy link
Contributor Author

Numpsy commented Sep 20, 2024

Ok, I'll leave until the .NET 8 changes are done

@xperiandri
Copy link
Collaborator

Should we already merge this?

@Numpsy
Copy link
Contributor Author

Numpsy commented Sep 22, 2024

Is there going to be a 6.1.2 with any of the other more minor changes, or is just in to version 8 now?

Also needs a release note entry

let createPullRequest owner repoName (pullRequest: NewPullRequest) (client: Async<GitHubClient>) =
retryWithArg 5 client
<| fun client' -> async { return Async.AwaitTask <| client'.PullRequest.Create(owner, repoName, pullRequest) }
<| fun client' -> async { return! Async.AwaitTask <| client'.PullRequest.Create(owner, repoName, pullRequest) }
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we really need to wrap that into async CE?

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.

Is the return type of Fake.Api.GitHub.createPullRequest supposed to be Async<Async<PullRequest>> ?

2 participants