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

Roles: User - View Relation error #1038

Closed
3 tasks done
camdagr8 opened this issue Mar 29, 2019 · 1 comment
Closed
3 tasks done

Roles: User - View Relation error #1038

camdagr8 opened this issue Mar 29, 2019 · 1 comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@camdagr8
Copy link

camdagr8 commented Mar 29, 2019

I'm having trouble with the Role's View Relation button. It errors out if you click it after altering the columns for the Roles table.

  • You're running version >=1.2.23 of Parse Dashboard.
    Uh, no, only 1.2.0 is available.

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

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

Environment Setup

Parse Dashboard: 1.2.0
Parse Server: 3.1.3
Node: 11.3.0

Steps to reproduce

  1. Navigate to the Roles list
  2. Add a new column
  3. Click the 'View Relation' button for the user relation.

I noticed that if you click the 'refresh' button after the above steps, you can see the user relations.

Logs/Trace

Uncaught TypeError: n.map is not a function
    at _ (dashboard.bundle.js:20)
    at r.render (dashboard.bundle.js:20)
    at d._renderValidatedComponentWithoutOwnerOrContext (dashboard.bundle.js:20)
    at d._renderValidatedComponent (dashboard.bundle.js:20)
    at d._updateRenderedComponent (dashboard.bundle.js:20)
    at d._performComponentUpdate (dashboard.bundle.js:20)
    at d.updateComponent (dashboard.bundle.js:20)
    at d.receiveComponent (dashboard.bundle.js:20)
    at Object.receiveComponent (dashboard.bundle.js:6)
    at Object.updateChildren (dashboard.bundle.js:20)
@stale
Copy link

stale bot commented May 13, 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 May 13, 2019
@stale stale bot closed this as completed May 20, 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

1 participant