Better support for Arrays and Objects#1650
Better support for Arrays and Objects#1650dblythy wants to merge 2 commits intoparse-community:masterfrom
Conversation
|
Danger run resulted in 1 warning; to find out more, see the checks page. Generated by 🚫 dangerJS |
|
@dblythy line 260 should technically be Also, why is line 289 set as Edit: Line 289 is from 80d42a8. I think line 287 in |
|
Thank you for looking over this @pmmlo! I'll make the changes |
|
You may want to consider this for Object type. I tried to keep it consistent with your coding style. I wrote this in comments, so I can't promise that it's error free. Also, I think you missed a contentArray.push for date and boolean subtypes. Edit: Ok, I ran a couple tests, and made some additional edits. Here is my recommendation: Here is the Array and Object cell type conditions together. I tested some of the conditions, so fairly confident there are no typos. |
|
@pmmlo the style is a bit messy - I was trying to be consistent with the original code. I can share my branch with you if you're interested in contributing to this PR? If not no worries - i'll add your changes in later. |
BTW I'm now seeing the end bracket also needs to move out of the for loop. Otherwise, there will be end brackets after each array entry. |
|
Ok, all good @pmmlo. I'll work on your suggestions. I appreciate your support. I'm not a react developer so I've sorta winged this feature together, as it's frustrated me not having the array support. Any suggestions from more experienced developers are always welcomed. Thanks mate 👍 |
Don't sweat it. I am personally not a fan of react. If you are just getting into js view libraries/frameworks, you may want to check out vue.js as well. |
|
I 100% agree. I actually code primarily with vue + parse. It’s so much cleaner than react. |
Closes #1627
Edit: Just realised I still have to add support for Objects