feat: add pointer representation by a chosen column instead of objectId

[fn-faisal]

Issue 151 link

• The resolution implemented in this PR for this issue is to give users access to an option in the menu where they can change the default key for a given class.
• Throughout the Dashboard, anywhere that there is a pointer to this class object, the specified key's value (chosen in the edit menu option -> change pointer key) is used instead of objectId.
• The way the cells load data has been updated to support async loading and fetching of data. It now uses component states to hold and display updates to the browser cell.

If no key is specified, the pointer value falls back to objectId.

Caveat

There's no caching mechanism for pointer so if the same pointer value ( class objectID ) is used in multiple rows, it'll query DB for each of the new row.

[fn-faisal]

I will revert the package-lock.json but I'd need to add sweet alert dependency.

[mtrezza]

Thanks for this PR.

Can you please rename the PR title accordingly?

[fn-faisal]

Thanks for this PR.

Can you please rename the PR title accordingly?

I have updated the PR title.

[mtrezza]

Thank you.

• Does each cell trigger a separate query to fetch the representation, or is that done together with the paging mechanism as a bulk-fetch?
• Where is the information about the pointer key stored? Is it sustainable enough?
• Do we need the SweetAlert component? We already have existing components to achieve the same.

[fn-faisal]

Thank you.

• Does each cell trigger a separate query to fetch the representation, or is that done together with the paging mechanism as a bulk-fetch?
• Where is the information about the pointer key stored? Is it sustainable enough?
• Do we need the SweetAlert component? We already have existing components to achieve the same.

• For each cell, if the type is pointer and the pointer key is not objectId, it fetches the object using the get method of the Parse Query object.
• To store pointer data, localStorage is used to store Class name as key and the key as value.
• A similar PR was made using b4a dash and it has sweet alert so I went with it and this PR is based off of that one, but I can revert this to Parse Dashboard specific alter dialogue.

[mtrezza]

For each cell, if the type is pointer and the pointer key is not objectId, it fetches the object using the get method of the Parse Query object.

Can we make this more efficient and do a single query for all objects in sync with the paging mechanism?

A similar PR was made using b4a dash and it has sweet alert so I went with it and this PR is based off of that one, but I can revert this to Parse Dashboard specific alter dialogue.

Yes, it would be good if you could use the components we have. Every dependency is a cost factor for maintenance, security, etc. so we want to avoid adding new ones if they are not necessary.

[fn-faisal]

I've pushed a commit that will optimize the query. The second query has been removed and instead I've added include and select on the first query that fetches the data. I'll update the dialog in the upcoming commits.

[fn-faisal]

The dialogue to change pointer value has been updated. The sweet alert2 deps have been removed.

[mtrezza]

Great, kindly let me know when this is ready for review.

[fn-faisal]

I've cleaned up the code and the PR is ready to be reviewed.

[fn-faisal]

@mtrezza For the first issue regarding the pointers, I tried the steps above in the following video but could not reproduce the issue.

Screen.Recording.2021-09-29.at.9.31.49.PM.mov

[mtrezza]

Thanks, I'll take another look. Maybe you can take a look this meanwhile.

[mtrezza]

To make sure it doesn't get overlooked, the issue review is on hold because of #1723 (comment)

[fn-faisal]

@mtrezza I've reverted the changes for comment #1723 (comment)

[mtrezza]

Great, did you look through the whole PR if there are any other modifications that are not part of this PR?

[fn-faisal]

@mtrezza I went through the PR and it only seems to have changes related to pointer key issue.

[mtrezza]

Looks good! Amazing feature and great work 👏

[mtrezza]

🎉 This pull request has been released in version 3.3.0-alpha.2