-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Labels
block:majorNeeds to be resolved before next major release; remove label afterwardsNeeds to be resolved before next major release; remove label afterwardsbounty:$10Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)state:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagestate:released-alphaReleased as alpha versionReleased as alpha versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
A new pages router has been introduced with #7128. The PagesRouter
has since been thoroughly tested and can be moved out of experimental status.
For Parse Server 5.0-beta, the current router should be deprecated in favor of the new PagesRouter
.
Steps to reproduce
n/a
Actual Outcome
n/a
Expected Outcome
n/a
Environment
Server
- Parse Server version:
5.0.0-alpha.1
Metadata
Metadata
Assignees
Labels
block:majorNeeds to be resolved before next major release; remove label afterwardsNeeds to be resolved before next major release; remove label afterwardsbounty:$10Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)state:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagestate:released-alphaReleased as alpha versionReleased as alpha versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature