Paw comments

Results 6 comments of

Paw

from future import annotation and many to many example

yeah i lost loads of time to this, definitely think 'don't import annotations from future' should be stated somewhere in the docs. unless i missed it?

📝 Update docs to advise against using `from future import annotations`

YES!!! thankyou kind soul! i mean i already (eventually) found the issue, but its nice to see it going in the docs, itll save so many people so many headaches....

📝 Update docs to advise against using `from future import annotations`

> @pawrequest Are you able to review this PR? It looks like tiangolo has this repo locked down as he is virtually the only contributor done, but i have zero...

📝 Update docs to advise against using `from future import annotations`

@tiangolo please? the docs at least, but realistically this needs a custom exception or some other runtime feedback if it's at all feasible. each new user is almost guaranteed to...

Using Ublock Origin (likely other script blockers) breaks the generated gcode

doesn't happen to me, firefox 102, ublock origin

arrays in ModelForms - what can and can't be done atm?

yeah this is fine, but the modelform api makes it easier at the endpoint - i dont need to specify each field just a modeltype annotation. is the 'not fully...

Paw

from __future__ import annotation and many to many example

📝 Update docs to advise against using `from __future__ import annotations`

📝 Update docs to advise against using `from __future__ import annotations`

📝 Update docs to advise against using `from __future__ import annotations`

Using Ublock Origin (likely other script blockers) breaks the generated gcode

arrays in ModelForms - what can and can't be done atm?

from future import annotation and many to many example

📝 Update docs to advise against using `from future import annotations`

📝 Update docs to advise against using `from future import annotations`

📝 Update docs to advise against using `from future import annotations`