#Why do some routes not have names?

3 messages · Page 1 of 1 (latest)

trim canopy
#

Specifically, none of the routes that come from "django_eventstream" have names. This is annoying, because I cannot "reverse" them; if I change one of those URLs, I have to manually chase down all the clients and update them.

E.g. (cd project; poetry run python3 manage.py show_urls | poetry run tabulate) shows (it helps to use a really small font here, so that the columns align nicely)

/call/<hand_pk>/                                  app.views.table.details.call_post_view                  app:call-post
/events/all-tables/                               django_eventstream.views.events
/events/hand/<hand_id>/                           django_eventstream.views.events
/events/lobby/                                    django_eventstream.views.events
/events/partnerships/                             django_eventstream.views.events
/events/player/<channel>/                         django_eventstream.views.events
/events/table/<table_id>/                         django_eventstream.views.events
/events/top-sekrit-board-creation-channel/        django_eventstream.views.events
/hand/                                            app.views.hand.hand_list_view                           app:hand-list

In other words: the routes I created have names, but the eventstream ones don't 😦

#

I guess, since they're all the same view anyway, having a name wouldn't help any 😐

autumn raptor
#

Names are something the developer has to add manually in their urls.py, so presumably they're not there because django-eventstream developers haven't added them?