Skip to content

Find/first issue with 3.5 #1614

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

Closed
krtooch opened this issue Nov 18, 2022 · 7 comments · Fixed by #1600
Closed

Find/first issue with 3.5 #1614

krtooch opened this issue Nov 18, 2022 · 7 comments · Fixed by #1600
Labels
state:released Released as stable version state:released-beta Released as beta version type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@krtooch
Copy link

krtooch commented Nov 18, 2022

New Issue Checklist

Issue Description

Unable to user Query.first on 3.5

Steps to reproduce

Do a first() query with 3.5 client (the query work well with older versions, at least 3.4.2)

Actual Outcome

giving a collection 'Mission' the query above return an error

const t = await (new Parse.Query('Mission')) .select(['position', 'client']).equalTo('objectId', 'Etk9VWubwP')
           .first()
        console.log(t);

outputed error
Capture d’écran 2022-11-18 à 16 57 50

Expected Outcome

On lower version
the same query work.
Capture d’écran 2022-11-18 à 16 58 50

Environment

Issue found on 3.5, work on 3.4.2.

Server

  • Parse Server version: 5.3.3
  • Operating system: Alpine16
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): AWS

Database

  • System (MongoDB or Postgres): mongo
  • Database version: 4.4
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): ATLAS

Client

  • Parse JS SDK version: 3.5

Logs

@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Nov 18, 2022
@dblythy
Copy link
Member

dblythy commented Nov 18, 2022

3.5.0 is broken, please see #1600.

Can you try 3.5.1-alpha.2 or revert to 3.4.4

@mtrezza
Copy link
Member

mtrezza commented Nov 19, 2022

I'm closing, if the issue still exists on the latest alpha version please let us know and we'll re-open this issue.

@mtrezza mtrezza closed this as completed Nov 19, 2022
@dplewis
Copy link
Member

dplewis commented Nov 19, 2022

@mtrezza i think we should keep this open until the next stable release. More will come in. The checklist show a check mark for “existing” issues not closed ones

@mtrezza
Copy link
Member

mtrezza commented Nov 19, 2022

Yes, let me pin a new issue to the top of the issue list. Our process is that an issue is closed when the PR is merged. This also happens automatically because of the "Closes" tag on GitHub.

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 3.5.1-beta.2

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Nov 26, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 3.5.1

@parseplatformorg parseplatformorg added the state:released Released as stable version label Nov 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-beta Released as beta version type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants