You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the example below the child comment is in both the root list of comments and in child comments. This may bring a significant amount of extra data in some cases, so I propose to choose one way and drop the other one. Currently, in superhero-ui used nested comments and their duplicated are filtered out.
One more inconsistency is that the Profile key (by the way, why it from the capital letter?) defined in the root array elements, but missed in children comments.
In the example below the child comment is in both the root list of comments and in child comments. This may bring a significant amount of extra data in some cases, so I propose to choose one way and drop the other one. Currently, in superhero-ui used nested comments and their duplicated are filtered out.
One more inconsistency is that the
Profile
key (by the way, why it from the capital letter?) defined in the root array elements, but missed in children comments.https://raendom-backend.z52da5wt.xyz/comment/api/tip/1834_v1
Interestingly, the comment replies endpoint places children once in nested arrays. For example, "great!" reply in https://raendom-backend.z52da5wt.xyz/comment/api/756
The text was updated successfully, but these errors were encountered: