Skip to content
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

Just a little work confidence boost because I'd love this package to work well for a long time 😄 #2

Open
Khoding opened this issue Jan 25, 2022 · 2 comments

Comments

@Khoding
Copy link

Khoding commented Jan 25, 2022

Hi, so I just wanted to say: if you actually make this great and keep updating it, it'd be amazing. would really help with some of the problems the current error pages sometimes have. (would especially help if you managed to fix the infamous "error on line 1:1 of base.html" while it's actually not there at all).

Saying this because you explicitly say in your bio that you're terrible at updating repos (dw we all are 😂) thought giving you a little boost wouldn't hurt.
That's all, thanks for this package (not using it yet but I will when I get some time).

@kezabelle
Copy link
Owner

Hi there,
Thanks so much for reaching out with just plain positivity. I truly appreciate it :)

That's all, thanks for this package (not using it yet but I will when I get some time).

The fact that you've glanced at it encouragingly is enough, I certainly wouldn't expect you to be using it (yet), as it's still absolutely Work In Progress - bits of it still look terrible or haven't been refactored in yet, etc. I might still have debug guidelines turned on and so forth ;)

would really help with some of the problems the current error pages sometimes have. (would especially help if you managed to fix the infamous "error on line 1:1 of base.html" while it's actually not there at all).

So, there's some stuff I can "fix" (insofar as I might perceive issues), and some stuff that would ultimately have to get resolved upstream, which I'll probably do if I can make a case for them. The misleading errors would have to be fixed in Django-proper and may already be fixed or made more marginal now that there's a _culprit_node as of django/django@313c3d1 (ticket 28935). But possibly thorny issues remain there, and I've got some awareness of how irksome that kind of thing can be (that function was previously even longer and more complex ...)

Saying this because you explicitly say in your bio that you're terrible at updating repos (dw we all are 😂) thought giving you a little boost wouldn't hurt.

It's truly a wonderful sentiment; I'm (currently) hoping to keep this "up to date" enough that I can "finish" it to at least my satisfaction. Perhaps (delusions of grandeur!) I might get it to a point where discussions can be had about upstreaming it or something like it to the benefit of all.

Anyway, again, thanks. Open-Source is better because of people like you who offer goodwill.

@stribny
Copy link

stribny commented Feb 22, 2023

+1 on the package, the concept and design look amazing! Would love to see it finished :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants