New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Depends on Jinja2? #24
Comments
Oh cool, I hadn't seen your package! Nice that you have the livereload logic to replace things like CSS. Perhaps I will try add that here. I haven't done anything special to handle connection closing. Perhaps my package's use of a
Ah very good point - I need to make that a cautious import. I have an idea how. |
A cursory glance at the SSE view suggests you don't have the same issue, hence the kudos and head-scratching. Apologies if I wasn't clear enough! The simple test I did was to generate a new
Yeah there's a few niceties I added as I got further in and frustrated by the reloads themselves. That idea specifically comes from Phoenix, but another one you may end up finding yourself wanting is persistence of form data/scroll position/focus'd element, of debouncing multiple changes into one when the tab isn't active. YMMV. |
Yeah those sound nice. Right now I just want to do the simplest thing that works, most of the time. |
Python Version
3.9.5
Django Version
4.0
Package Version
main
Description
Hey Adam,
Saw this on your blog (via the Django subreddit) and came here to see how you'd ended up doing things - mostly to see how you'd solved some of the thorny issues related to cancelling the SSE's WSGI request on client hang-up (because I have a similar package and I had to do some hacks!) ... and actually I don't know how in the world you've done it, but done it you have, kudos (I'd love to know which bit is solving it, if you're feeling generous at any point)
Anyway, trying to set it up to explore the hang-up situation, I encountered the following exception:
Naturally it's easy enough to resolve (installed jinja2), but thought you might want to know.
The text was updated successfully, but these errors were encountered: