Piet van Leeuwen
Piet van Leeuwen
Possible option.? https://github.com/timchurch/django-color-utils/blob/master/color_utils/utils.py#L4
Use MeQuery - I have removed UserQuery, quite dangerous to leave it in there. If you want to add a user specific mutation/query you can use the verification_required. No docs...
Using vanilla js, I found this worked. ``` javascript // force options to transition instantly featureFlkty.options.selectedAttraction = 1; featureFlkty.options.friction = 1; // select item featureFlkty.select(i); // reset defaults featureFlkty.options.selectedAttraction =...
Is this the idea of PolymorphicSortableAdminMixin- https://github.com/jrief/django-admin-sortable2/blob/3c7c8c34a07c8d522d8f6c5216f0e0a6180730a9/adminsortable2/admin.py#L419
Possible that this is a typescript/node issue - Swapping out with - ``` id: number; data: { name?: string; surname?: string; }; ``` rather than ``` id: number; data: UpdateUserDto;...
I've changed this to - ``` async ({ id, ...data }: { id: number } & UpdateUserDto): Promise => { ``` And now it compiles correctly. This is potentially a...
Yeah seems to not recognise the type/interface from children, this test also fails - ``` type Other = { id: number; } async ({ id, ...data }: { id: number;...
This issues persists, I'm on the latest version `1.46.4`. It seem to be that the issue appears when using a defined type. Some examples below. The following example fails -...
When I visit `http://localhost:9400/...` it seems to still recognise the types values.