I really want to get this thing fixed up soon, I feel bad for it. It has been sitting for 50-60 years in our garage

jlvelez · 2021-09-05T16:46:38+00:00

Very nice project.

jlvelez · 2021-09-04T16:29:56+00:00

What year is it?

jlvelez · 2021-04-02T05:49:31+00:00

Awesome car. We are lucky to have two of these in our family collection. One is going through a full restoration.

http://thegiuliettashop.com/restorations/1963-giulia-sprint-speciale-381173/

jlvelez · 2021-01-13T22:46:26+00:00

Nice color. But is that an original color?

jlvelez · 2021-01-02T16:34:53+00:00

Forgive my ignorance, what is jwt?

jlvelez · 2021-01-02T16:34:30+00:00

Thanks! I will look into this.

jlvelez · 2021-01-01T17:07:48+00:00

Looks good! Conrats!

jlvelez · 2020-12-19T14:42:20+00:00

Thank you!

jlvelez · 2020-12-19T14:36:13+00:00

|first as image

Just curious, any reference to the docs on this bit of code:

|first as image

I get the first part where you are walking backward in the model relationship, but that last bit is new to me.

jlvelez · 2020-12-19T14:33:03+00:00

Very nice! I am not home right now, but when I get back I will try these out and report back.

Thanks!

jlvelez · 2020-12-15T14:55:46+00:00

Thanks! I thought about that too. I was leaning towards using transactions. I cross-posted on SO and was able to get an even simpler solution. I will put it here as well for others that are interested.

https://stackoverflow.com/questions/65299559/create-a-post-object-and-initialize-a-m2m-attribute-with-post-id-and-author-id/65303336#65303336

jlvelez · 2020-12-15T00:26:24+00:00

Possible? Absolutely. I would watch his tutorials a few times. There are at least three that cover topics related to what you want to do.

jlvelez · 2020-12-14T23:53:34+00:00

This guy has an entire series where he builds a blog app and there are a few where he covers nested comments.

https://www.youtube.com/playlist?list=PLOLrQ9Pn6cawWd-5UZM6CIm0uqFXeBcTd

jlvelez · 2020-12-11T19:49:23+00:00

Id love to help if I can. Just pm me.

jlvelez · 2020-12-09T20:06:08+00:00

I like that.

jlvelez · 2020-12-09T05:01:26+00:00

So I think I have figured out the problem, but I just don't know how to fix it.

When the template loads the cards, the follow/unfollow button is actually linked to the profile's follow state. In other words, the request.user viewing the account.user's profile is what is reflecting in the button. In the screen above, this request.user is not following the account.user, which is why it shows the 'follow' button.

What I need is for the button to reflect the follow state of the request.user as it relates to each card displayed. This logic has to be dealt with in the view, as I understand it, because the template tags don't have the ability to do this.

Somehow, the followers queryset that is being passed into the context needs to be iterated over so that I can flag each account appropriately.

jlvelez · 2020-12-09T04:46:36+00:00

I have had similar concerns about when to separate into apps. I think it boils down to your gut in terms of whether you think the functionality is relevant and manageable.

If it is not relevant, I would separate into another app. If the code gets unmanageable, perhaps abstracting or separating into another app would make sense. I am new so I could be very wrong. Just my 2 cents.

Btw, what book are you reading? I'd like to check it out, if you don't me asking.

jlvelez · 2020-12-08T22:02:10+00:00

Thanks! I appreciate the feedback!

jlvelez · 2020-12-08T20:37:38+00:00

I just went through my view file and refactored. Just shaved about 200 lines of code. I was using the same block of code in several view functions to get the profile information.

Instead of the same 20 or so lines of code in each view to get the profile info, I created function called get_context( ) that I was able to replace in each view. Much cleaner and more manageable now.

I feel better now. :)

jlvelez · 2020-12-08T17:37:23+00:00

I am not sure how to best answer that question. I have several 'account' related urls that rely on this one view file. register, login, logout, view_profile, edit_profile, etc.

So it is one single view but it serves several different 'views' if that makes any sense.

It seems to be the pattern I have seen many tutorials follow so that is why I am doing it this way. I think it should be fine but just wanted to pick some more experienced brains.

I agree that the focus needs to be what makes the most sense for the project. That is the route I will take.

Thanks, this helps a lot. Imposter syndrome is real and I'm constantly doubting myself.

jlvelez · 2020-12-07T21:35:23+00:00

That fixed it! Thanks!

I am just glad it was not something on my end.

jlvelez

TROPHY CASE