Skip to content

When appName has a '#', dashboard doesn't work. #529

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
yomybaby opened this issue Sep 12, 2016 · 6 comments
Closed

When appName has a '#', dashboard doesn't work. #529

yomybaby opened this issue Sep 12, 2016 · 6 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@yomybaby
Copy link

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

  • [O] You're running version >=1.0.18 of Parse Dashboard.
  • [O] You're running version >=2.2.18 of Parse Server.
  • [O] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Steps to reproduce

  1. make config.json.
    Make sure appName has a '#' letter.
{
  "apps": [
    {
      "serverURL": "https://api.server.com/parse",
      "appId": "myappid",
      "masterKey": "mymasterkey",
      "appName": "#[REAL] Parse",
      "production": true
    }]
}
  1. run dashboard parse-dashboard --config config.json
  2. click your "#[REAL] Parse" app on your dashboard app list.

BUT, it doesn't work. there is no error.

@pie6k
Copy link

pie6k commented Oct 21, 2016

I think it's quite normal to assume that name and slug should not include special characters.

@gowridev
Copy link

its doesn't even takes spaces

@flovilmart
Copy link
Contributor

Spécial chars are not supported like # and ? As the app name is not encoded. Does someone want to take a knock at it?

@dvanwinkle
Copy link
Contributor

@flovilmart Would the better solution be to not allow the appName to include these characters or to support them?

@flovilmart
Copy link
Contributor

We could do that too. I don't have a strong opinion on that one.

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Jan 10, 2019
@stale stale bot closed this as completed Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

5 participants