refactor: change example config Parse Server port from 1338 to 1337#2012
Merged
mtrezza merged 1 commit intoparse-community:alphafrom Jan 23, 2022
Merged
Conversation
Thanks for opening this pull request!
|
4 tasks
mtrezza
changed the title
Contributor
|
🎉 This change has been released in version 4.0.0-alpha.13 |
Contributor
|
🎉 This change has been released in version 4.0.0-beta.3 |
Contributor
|
🎉 This change has been released in version 4.0.1 |
beiguancyc
pushed a commit
to beiguancyc/parse-dashboard
that referenced
this pull request
Mar 4, 2022
* source: (43 commits) chore(release): 4.0.1 [skip ci] ci: release commit chore(release): 4.0.0-beta.3 [skip ci] ci: release commit refactor: upgrade prismjs from 1.25.0 to 1.26.0 (parse-community#2019) chore(release): 4.0.0-alpha.15 [skip ci] fix: preserve column sorting preferences in data browser (parse-community#2016) refactor: upgrade prop-types from 15.8.0 to 15.8.1 (parse-community#2018) refactor: upgrade otpauth from 7.0.8 to 7.0.9 (parse-community#2017) chore(release): 4.0.0-alpha.14 [skip ci] fix: crash when checking for new dashboard release without internet connection (parse-community#2015) chore(release): 4.0.0-alpha.13 [skip ci] fix: calendar widget layout partly hides last days of a month (parse-community#1990) refactor: change example config Parse Server port from 1338 to 1337 (parse-community#2012) chore(release): 4.0.0-alpha.12 [skip ci] fix: upgrade parse from 3.4.0 to 3.4.1 (parse-community#2011) chore(release): 4.0.0-alpha.11 [skip ci] fix: various UI bugs (e.g. filter data browser, switch app, upload file) (parse-community#2010) chore(release): 4.0.0-alpha.10 [skip ci] fix: bump nanoid from 3.1.28 to 3.2.0 (parse-community#2008) ... # Conflicts: # package-lock.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Pull Request Checklist
Issue Description
Change the Parse Server port in the dashboard example config file from 1338 to 1337. This is also the default port of Parse Server, so it makes sense for Parse Dashboard to also talk to that port by default. This should is not considered a breaking change as the config file is merely an example config file that also includes other "example values" like
helloandworldas username and password.Related issue: #2013
Approach
Change port 1338 to 1337.
TODOs before merging