Skip to content
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

feat: Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in example web page #562

Merged
merged 18 commits into from
Mar 6, 2025
Merged

feat: Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in example web page #562

merged 18 commits into from
Mar 6, 2025

Conversation

dblythy
Copy link
Member

@dblythy dblythy commented Jan 13, 2025 •
edited
Loading

Closes: #558
Closes: #398
Closes: #396
Closes: #399

@parse-github-assistant Parse GitHub Assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title feat: update example feat: Update example Jan 13, 2025
@parse-github-assistant Parse GitHub Assistant
Copy link

parse-github-assistant bot commented Jan 13, 2025 •
edited
Loading

Thanks for opening this pull request!

@mtrezza
Copy link
Member

mtrezza commented Jan 13, 2025 •
edited
Loading

Which issue does this PR close? Is it #558?

@dblythy
Copy link
Member Author

dblythy commented Jan 13, 2025

Yes sorry

@mtrezza mtrezza changed the title feat: Update example feat: Update example to Parse Server 8 Jan 13, 2025
@dblythy
Copy link
Member Author

dblythy commented Jan 14, 2025 •
edited
Loading

Some QOL improvements here:

  • using ESM
  • using the JS SDK in the demo file
  • presenting an opinionated folder structure and class design that should allow for better testability
  • adding unit tests that can run very fast and in parallel
  • simplification of the CI - no need to have multiple node versions

@mtrezza
Copy link
Member

mtrezza commented Jan 16, 2025 •
edited
Loading

Great work, just about these:

  • presenting an opinionated folder structure and class design that should allow for better testability
  • adding unit tests that can run very fast and in parallel

I appreciate the approach to apply a theoretical best-practice, but for this simple repo it seems a bit much. We want to keep this repo as slim as possible to demo Parse Server in a light weight, few dependencies, low maintenance repo.

Parallel testing, new test framework with jest, etc. are out of scope; we want to avoid that at some point in the future we have to spend time fixing this, as it's not the purpose of this repo. Could you please keep the structure and nomenclature we are currently using across most repos (/spec) and remove the subfolders "Hello", etc. Just a test file with the same name as the file that is being tested should provide enough overview, e.g. /spec/TestObject.spec.js.

@dblythy
Copy link
Member Author

dblythy commented Jan 21, 2025

Only showing testing as e2e testing is not overly great IMO and does little to educate users of the platform of the benefit of a proper test suite. But I'll walk it back.

mtrezza
mtrezza reviewed Jan 21, 2025
View reviewed changes
mtrezza
mtrezza approved these changes Jan 28, 2025
View reviewed changes
Copy link
Member

@mtrezza mtrezza left a comment •
edited
Loading

Choose a reason for hiding this comment

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

Looks good, removing the Node matrix was a good idea; just need to wait to upgrade to stable release of Parse Server 8.

@mtrezza
Copy link
Member

mtrezza commented Mar 4, 2025

@dblythy PS8 has been released, could you please update the PR so this can be merged? Thanks!

mtrezza
mtrezza reviewed Mar 4, 2025
View reviewed changes
@mtrezza
Copy link
Member

mtrezza commented Mar 6, 2025 •
edited
Loading

BREAKING CHANGE: This release upgrades to Parse Server 8. See the Parse Server 8 change log for more details about breaking changes. This release also changes to using ES6 syntax.

@mtrezza mtrezza changed the title feat: Update example to Parse Server 8 feat: Update example to Parse Server 8 and use the Parse JS SDK in the example web page instead of native JavaScript Mar 6, 2025
@mtrezza mtrezza changed the title feat: Update example to Parse Server 8 and use the Parse JS SDK in the example web page instead of native JavaScript feat: Upgrade to Parse Server 8 and use the Parse JS SDK in the example web page Mar 6, 2025
@mtrezza mtrezza changed the title feat: Upgrade to Parse Server 8 and use the Parse JS SDK in the example web page feat: Upgrade to Parse Server 8 with ES6 syntax and use the Parse JS SDK in the example web page Mar 6, 2025
@mtrezza mtrezza changed the title feat: Upgrade to Parse Server 8 with ES6 syntax and use the Parse JS SDK in the example web page feat: Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in the example web page Mar 6, 2025
@mtrezza mtrezza changed the title feat: Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in the example web page feat: Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in example web page Mar 6, 2025
@mtrezza mtrezza merged commit 120e98f into parse-community:master Mar 6, 2025
3 checks passed
parseplatformorg pushed a commit that referenced this pull request Mar 6, 2025
@semantic-release-bot
chore(release): 3.0.0 [skip ci]
f4409cb 
# [3.0.0](2.0.0...3.0.0) (2025-03-06)

### Bug Fixes

* Bump express from 4.21.0 to 4.21.1 ([#531](#531)) ([4d5c64f](4d5c64f))

### Features

* Upgrade parse-server from 7.2.0 to 7.3.0 ([#529](#529)) ([76c6229](76c6229))
* Upgrade parse-server from 7.3.0 to 7.4.0 ([#553](#553)) ([2c40f21](2c40f21))
* Upgrade to Parse Server 8 using ES6 syntax and Parse JS SDK in example web page ([#562](#562)) ([120e98f](120e98f))

### BREAKING CHANGES

* This release upgrades to Parse Server 8. See the Parse Server 8 [change log](https://github.com/parse-community/parse-server/releases/tag/8.0.0) for more details about breaking changes. This release also changes to using ES6 syntax. ([120e98f](120e98f))
@parseplatformorg
Copy link

🎉 This change has been released in version 3.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mtrezza mtrezza mtrezza approved these changes

Assignees
No one assigned
Labels
state:released
Projects
None yet
Milestone
No milestone
3 participants
@dblythy @mtrezza @parseplatformorg