I tried to pass the comment._id in an hidden form manually to be used for adding likes

Manually inputting values not working about gettingmean-2 HOT 7 CLOSED

cliveharber commented on July 27, 2024

Manually inputting values not working

from gettingmean-2.

Comments (7)

cliveharber commented on July 27, 2024

From brief purely code read I can only identify the following:

The "hidden" field isn't actually hidden. In HTML hidden form fields have a type="hidden" rather than what you've put.
The "id" that you're logging out in onCommentVoteUpSubmit() doesn't exist in the given context, so will be undefined. What I think you wanted to log was this.newComment._id.

I hope this helps

from gettingmean-2.

walegbenga commented on July 27, 2024

What you said was what I did from the onset. i.e. this.newComment._id but it keeps returning error when compiled. It always complain that _id is not set in Comment class while it is set.

The problem is that am unable access any of the Comment field in the method

That is why I thought of doing it another way

P.s. am now able to get rid of the error, but still unable to pass the id from the form to the onCommentVoteUpSubmit()

from gettingmean-2.

cliveharber commented on July 27, 2024

The first question that comes to mind then is: why are you trying to set this data at the template level. If the comment id is already in the component, why not set it at at component level? So at the point where you need it. The form isn’t posting directly back to the server as you’re using ngModel. I assume that the comment data is already fully populated, so has already been submitted to the database in order to get the _id from MongoDB. If this is actually a brand new comment (which I suspect) and not a concept leak (which I also suspect), then newComment shouldn’t have an _id unless you’ve given it one - I think that you’re trying to do this, although I suspect that sending data with an already assigned _id field will cause the original comment to be overwritten - maybe this is what you’re shooting for, maybe it isn’t. So further questions as they’re not obvious from the code that you’ve pushed up: Are you trying to add voting to comments that are already submitted and display in the page as a list? In which case, why are you using a newComment class to hold that data? newComment shouldn’t have an _id field, it should only know of its content and maybe which post it is being attached to. You might need a different concept/class to hold the comments that you want to provide voting functionality for. Are you trying to add voting to newComment? In which case, does this make sense and also _id won’t be defined as newComment is exactly that, a new comment, and therefore hasn’t been submitted to the database yet. My feeling is that you’re mixing concepts in your page. A comment and a newComment might use the same class (Comment), but the comment is there to hold data for comments in the comments list and newComment is there for holding form data. The only thing a newComment should know about the voting system is that the upVote and downVote data is 0. It's the comments that care about voting and if you’re providing functionality like this, then maybe it's time to break the listing out into a list of components where each Comment component manages its own voting data. Clive Harber CTO // DistortedThinking e: [email protected] w: www.distortedthinking.agency t: +44 7815 166434

…

On 23 Sep 2020, at 08:02, Gbenga Ogunbule ***@***.***> wrote: What you said was what I did from the onset. i.e. this.newComment._id but it keeps returning error when compiled. It always complain that _id is not set in Comment class while it is set. That is why I thought of doing it another way — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHBJL7Q55DWP7WSLBAGGJ3SHGMQJANCNFSM4RWLRF3Q>.

from gettingmean-2.

walegbenga commented on July 27, 2024

why are you trying to set this data at the template level

From the onset, I thought the comment id is available in the component level but when I use this.comment._id, it returns

Undefined

I thought, it I could get it that way. I tried this.post.comments._id, it also returned

Undefined

That is why I chose the part of template component.

If this is actually a brand new comment (which I suspect)

This is not a brand new comment. USER A makes a comment, USER B, after reading the comment, click on the LIKE button to like the comment.

_I suspect that sending data with an already assigned id field will cause the original comment to be overwritten - maybe this is what you’re shooting for, maybe it isn’t.

No, that is not am aiming for.

Are you trying to add voting to comments that are already submitted and display in the page as a list?

Yes, that is my goal.

In which case, why are you using a newComment class to hold that data?

Reason why I did that is not far fetched, I simply wanted to use the newComment for creating (1) a new comment (2) updating an existing comment (3) using it in voting system.

This is what am trying to achieve.

Am sorry for incessant messages. That is due to a newbie trying to get to the professional level

from gettingmean-2.

cliveharber commented on July 27, 2024

As what you’re doing isn’t related to issues with the book text which is what this repo/issues list is for and beyond the scope given in that book, message me directly at [email protected] <mailto:[email protected]> and I will see what I can do to help you. Cheers Clive Harber CTO // DistortedThinking e: [email protected] w: www.distortedthinking.agency t: +44 7815 166434

…

On 23 Sep 2020, at 12:37, Gbenga Ogunbule ***@***.***> wrote: why are you trying to set this data at the template level From the onset, I thought the comment id is available in the component level but when I use this.comment._id, it returns Undefined I thought, it I could get it that way. I tried this.post.comments._id, it also returned Undefined That is why I chose the part of template component. If this is actually a brand new comment (which I suspect) This is not a brand new comment. USER A makes a comment, USER B, after reading the comment, click on the LIKE button to like the comment. _I suspect that sending data with an already assigned id field will cause the original comment to be overwritten - maybe this is what you’re shooting for, maybe it isn’t. No, that is not am aiming for. Are you trying to add voting to comments that are already submitted and display in the page as a list? Yes, that is my goal. In which case, why are you using a newComment class to hold that data? Reason why I did that is not far fetched, I simply wanted to use the newComment for creating (1) a new comment (2) updating an existing comment (3) using it in voting system. This is what am trying to achieve. Am sorry for incessant messages. That is due to a newbie trying to get to the professional level — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHBJL5MKOROPKIXXLFITIDSHHMXFANCNFSM4RWLRF3Q>.

from gettingmean-2.

walegbenga commented on July 27, 2024

I have message you.

Thanks so much

from gettingmean-2.

cliveharber commented on July 27, 2024

I've replied. I'm going to close this now.

from gettingmean-2.

Manually inputting values not working about gettingmean-2 HOT 7 CLOSED

Comments (7)

Related Issues (11)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent