Skip to content

first: Correct return type #662

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 14, 2021
Merged

first: Correct return type #662

merged 1 commit into from
Sep 14, 2021

Conversation

sils
Copy link

@sils sils commented Aug 2, 2021

Fixes #661

@RodrigoSMarques RodrigoSMarques changed the base branch from master to development August 2, 2021 22:33
@RodrigoSMarques
Copy link
Contributor

Thank you for your contribution

@RodrigoSMarques RodrigoSMarques merged commit 149d250 into parse-community:development Sep 14, 2021
@mtrezza mtrezza mentioned this pull request Oct 18, 2021
Closed
@fischerscode fischerscode mentioned this pull request Nov 15, 2021
Merged
5 tasks
@sils
Copy link
Author

sils commented Feb 22, 2022

Hey, this has been a while now, any idea on when the next release is happening?

@mtrezza mtrezza mentioned this pull request May 30, 2022
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

type 'Null' is not a subtype of type 'FutureOr<ParseObject>'
2 participants
@sils @RodrigoSMarques