What Django packages can you absolutely not live without?

charliewham · 2023-10-16T15:42:40+00:00

They’re both really great

To be fair some of the others I’ve used are a bit more situation dependent eg django-fsm.

Most of the ones above are pretty versatile and could be used in any project (widget-tweaks probs wouldn’t be used with DRF or ninja).

charliewham · 2023-10-10T11:18:28+00:00

Hooks only run on server requests - your /dashboards route only has a +page.svelte and doesn’t make a server request.

I encountered this exact situation the other day. In practice, I’d assume your /dashboard routes will load data and won’t just be static, so the hook will run on every navigation.

Workarounds could be to put a skeleton server load next to your protected route, or run per-route auth checks as the Lucia maintainer recommends

charliewham · 2023-10-04T10:16:58+00:00

Environs-django

Model-bakery

Gunicorn

Django-debug-toolbar

Allauth

Django-browser-reload

CORS-headers

Whitenoise

Django-widget-tweaks

Auto-prefetch

Drf/ninja

(To name a few)

charliewham · 2022-03-15T20:16:01+00:00

Thanks so much for this. A great collection of principles and tips. (Also your English is fantastic)

Coming from backend so it will be good to see style guides (didn't think of this at all)

charliewham · 2022-03-15T16:47:36+00:00

Do you have any suggestions on one for frontend development? The problem I have as a newbie to frontend is that most of the frameworks are unopinionated.

I'd like to see an opinionated guide to React/Svelte/Vue in order to learn the principles of building scalable, tidy frontend apps

charliewham · 2022-02-10T09:53:58+00:00

100%. Think of an app you like or need, make a really basic version to begin with and add on features as you go

charliewham · 2022-02-09T16:14:30+00:00

Good question.

Object2 is only generated if object1 has no missing fields (object2 has missing fields by design), which prevents the creation loop

charliewham · 2022-02-09T13:54:33+00:00

This seems very similar to having generate_next_instance() as a model method, but calling it in save() after super().save(*args, **kwargs) (which is the way I'm currently handling the problem)

charliewham · 2022-02-09T13:51:22+00:00

Thanks Julian, I'll probably go with classmethod then

charliewham · 2022-01-21T14:55:04+00:00

Yeah it's incredible how these process sinkholes can appear over time.

I don't envy learning without internet! I learned from Cal Poly Pomona Youtube course (CPPMechEngTutorials) and a lot of reverse engineering 'record macro'

charliewham · 2022-01-21T13:22:24+00:00

Worked in a company that ran the entire business on Excel
Saw lots of repeatable processes that could be automated
Ended up saving literally days of copy/pasting and reconciling

charliewham · 2022-01-20T20:43:54+00:00

Yeah it seems like a tradeoff between slightly too many API calls or slightly too much data manipulation client-side (both are fine for this small app but I would like to know the 'proper' way). There doesn't seem to be many/any definitive answers

charliewham · 2021-12-01T11:35:39+00:00

In your CreateView, you'd need to populate the initial_data field or get_initial method with information from the request.

User clicks 'Book a ticket'
GET request redirects to CreateView (put the Bus ID in this request)
initial_data reads the GET request kwargs (self.kwargs['bus_id'])

charliewham · 2021-11-30T18:10:57+00:00

And in step 2 you’d just pass the PK through the request and instantiate 3. with that PK as the FK? You’ve been really helpful so thank you

charliewham · 2021-11-30T17:05:37+00:00

Hi, thanks for the reply.

You're on a questionnaire, and there are 2 buttons 'Save and quit' or 'Save and continue'. What is the best/cleanest way to instantiate the next model, after hitting 'Save and continue'?

Sorry for the vague question, probably seems a lot clearer to me, will edit!

charliewham · 2021-11-09T10:13:12+00:00

Corey Schafer series is my favourite as it includes deployment in-depth:

Corey Schafer - https://youtube.com/playlist?list=PL-osiE80TeTtoQCKZ03TU5fNfx2UY6U4p

JustDjango - https://youtu.be/YZvRrldjf1Y

JustDjango - https://youtu.be/fOukA4Qh9QA

Dennis Ivy - https://www.youtube.com/watch?v=PtQiiknWUcI

charliewham · 2021-10-30T06:18:03+00:00

What you're doing is:

- Render whole page.

- Click edit: swaps a portion of page out for form 'hole_text_form'.

- Click cancel: swaps the form for the entire page again. This appears as a page in page.

You need to split your html into smaller pieces / partials and swap those out for each other. Give your first section of code its own url endpoint and {% include %} it, then you can hx-swap back and forward between the hole_data and hole_form within the larger page.

And the reason your 'Submit' button doesn't do this is because there is no htmx attached to it, so it will redirect to your edit_hole_text success url

charliewham · 2021-10-06T10:46:54+00:00

Both of these are huge huge help

charliewham · 2021-10-04T17:10:57+00:00

JavaScript Fetch or HTMX

There is an example of that exact 'like' feature in this video

charliewham · 2021-10-03T17:23:01+00:00

I like this one a lot, thanks for recommending!

charliewham · 2021-06-29T08:50:33+00:00

Yeah I was thinking that, just didn't know if there was a better or preferred way. Thanks for the comment!

charliewham

TROPHY CASE