I know that there are several ways to do this.
Do you think it makes sense to add a chapter about this?
--
Ticket URL: <https://code.djangoproject.com/ticket/32854>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
> Imagine you want to use third-party JS code like https://tom-
> select.js.org/ or https://d3js.org/
>
> I know that there are several ways to do this.
>
> Do you think it makes sense to add a chapter about this?
New description:
Imagine you want to use third-party JS code like https://tom-
select.js.org/ or https://d3js.org/
I know that there are several ways to do this.
Do you think it makes sense to add a chapter about this?
I know there are thousand ways to do this. For this topic there is no
"single source of truth".
But the docs could list some feasible ways, so that new users are not
completely lost.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32854#comment:1>
Old description:
> Imagine you want to use third-party JS code like https://tom-
> select.js.org/ or https://d3js.org/
>
> I know that there are several ways to do this.
>
> Do you think it makes sense to add a chapter about this?
>
> I know there are thousand ways to do this. For this topic there is no
> "single source of truth".
>
> But the docs could list some feasible ways, so that new users are not
> completely lost.
New description:
Imagine you want to use third-party JS code like https://tom-
select.js.org/ or https://d3js.org/
I know there are thousand ways to do this. For this topic there is no
"single source of truth".
But the docs could list some feasible ways, so that new users are not
completely lost.
Do you think it makes sense to add a chapter about this?
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32854#comment:2>
* status: new => closed
* resolution: => duplicate
Comment:
Duplicate of #30296
--
Ticket URL: <https://code.djangoproject.com/ticket/32854#comment:3>