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.

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

conflict in appName in ParseDashboard #998

Closed
3 tasks done
nasermirzaei89 opened this issue Feb 20, 2019 · 1 comment
Closed
3 tasks done

conflict in appName in ParseDashboard #998

nasermirzaei89 opened this issue Feb 20, 2019 · 1 comment

Comments

@nasermirzaei89
Copy link

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

  • You're running version >=1.0.23 of Parse Dashboard. (1.2.0)

  • You're running version >=2.3.2 of Parse Server. (3.1.3)

  • You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Steps to reproduce

1- Create 2 parse servers
2- Add both in Parse dashboard with the same appName
3- goto dashboard and you will see a conflict on app info and data, because of same name
for example
https://parse-dashboard/apps/AppName/browser/_Role
for both servers

Logs/Trace

Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.

Suggestion

use app id in URL for avoiding conflict!

@dplewis dplewis added the type:bug Impaired feature or lacking behavior that is likely assumed label Mar 20, 2019
@acinader
Copy link
Contributor

acinader commented Apr 3, 2019

Is this really a bug? I don't think so. This is really more of a JSON issue than a parse dashboard issue.

We don't want to get into pre-processing the JSON to check for duplicate keys:

https://esdiscuss.org/topic/json-duplicate-keys

We could add something to the docs to warn if someone wants to take that on...

@nasermirzaei89 do you have a recommended solution? I think this is a 'wont fix'

@acinader acinader added state:wont-fix Won’t be fixed with a clearly stated reason and removed type:bug Impaired feature or lacking behavior that is likely assumed labels Apr 5, 2019
@stale stale bot removed the state:wont-fix Won’t be fixed with a clearly stated reason label Apr 5, 2019
@acinader acinader closed this as completed Apr 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants