parse-dashboard
parse-dashboard copied to clipboard
parse-community
Arrays of Pointers dont render correctly
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
- [x ] You're running version >=2.1.4 of Parse Server.
- [x ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
Steps to reproduce
Pointers render with a link to the object its pointer to, unless that pointer is in an array.
[{"__type":"Pointer","className":"Connection","objectId":"8vCiwc7J1T"},{"__type":"Pointer","className":"Connection","objectId":"HHv9Oa6qFE"},{"__type":"Pointer","className":"Connection","objectId":"LTRsJIYBIH"}]
It would be nice if the pointers in an array rendered and linked to the object its pointing to as well.
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.
Could the same parsing that is done on 'pointer' columns be applied when __type:Pointer is identified in the array?
Therr is rreally no point to be using Parse these days.
Why? Any valid alternative to suggest?
Firebase? AWS?
On Mon, Dec 9, 2019 at 1:34 PM AntonelloCherry [email protected] wrote:
Therr is rreally no point to be using Parse these days.
Why? Any valid alternative to suggest?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/parse-community/parse-dashboard/issues/275?email_source=notifications&email_token=AAD63FM22ZS45CDHOKV55BTQX2FRTA5CNFSM4CBI2ZGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGKFZJQ#issuecomment-563371174, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD63FMD4OZGVD7ULSVXHCLQX2FRTANCNFSM4CBI2ZGA .
-- [image: photo] Ken Kyger Founder, FutureHax Development http://www.linkedin.com/in/r2doesinc/ http://github.com/futurehax http://stackexchange.com/users/1130968/r2doesinc http://twitter.com/r2DoesInc 407.965.8510 [email protected] Skype: r2doesinc <#SignatureSanitizer_SafeHtmlFilter_> futurehax.org The best way to predict the future, is to create it. Click here to schedule a meeting https://calendly.com/futurehax
IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please notify the sender immediately and do not disclose the contents to anyone or make copies thereof.
@r2DoesInc I believe it was decided to make Array and Object fields to be generic as possible. This fixed a lot of decoding issues from the database.
Your feature request is still up for grabs. Unfortunately we don't have enough React developers in this Dashboard repo.
@AntonelloCherry Would you like to open a PR to addressed this? We are more than welcome to help.
Parse is quite active and better than ever!
Therr is rreally no point to be using Parse these days.
Maybe not for you, but this is a very active community and there are still quite a few people using it. Yes there are alternatives, but some may prefer to avoid 'the great Google in the sky' or other options and Parse is a strong, open source alternative.