Skip to content

Conversation

@marcusgadbem
Copy link
Contributor

Hi! I was playing around with Parse server and realized that we could make couple requests from the frontend to the local Parse server (also the cloud code) in order to ensure things are running properly.

This PR contains the page and buttons that helps making those tests easier.
Hope it helps! :)

…e example

* Add assets to compose the screen
* Update express package version to properly serve the HTML
@hramos
Copy link
Contributor

hramos commented Mar 14, 2016

This is something we've thought about exploring. Several guides do mention that people should look for the "I dream of being a web site" message, so I wouldn't replace the default landing page just yet to avoid any confusion. Can you host this under a different route?

Also, in future PRs that add to the static site it would be useful to include a screenshot of the generated page in the PR description, for review purposes.

@marcusgadbem
Copy link
Contributor Author

Nice. I'm changed root route back to the message and moved test screen to a route named /test.
Also made a little fix in CSS pre rule to avoid test's output to overflow the box.

Since we are moving the screen to a different route than the root, would be nice to improve README.md#using-it instructions which I also added to this PR if you don't mind.
I still can make any changes if you want me to.

Still for documentation, here are the screenshots of the proposed screen:

parse-ss-1
parse-ss-2
parse-ss-3
parse-ss-4

hramos added a commit that referenced this pull request Mar 16, 2016
Add a page to assist users to test the parse server
@hramos hramos merged commit 62c8282 into parse-community:master Mar 16, 2016
@hramos
Copy link
Contributor

hramos commented Mar 16, 2016

This is great! Thanks a lot.

@parseplatformorg
Copy link

🎉 This change has been released in version 1.2.0

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants