t; >> > ```html
>>>> >> >
>>>> >> >
>>>> >> > function foo1 (aa, bb)
>>>> >> >
>>>> >> > /*
>>>> >> > * this function will blah blah blah
>>>> >&
gt;>> >> > /*
>>> >> > * this function will yada yada yada
>>> >> > */
>>> >> >
>>> >> >
>>> >> >
>>> >> > ```
>>> >> >
>>> >> >
>>> >> > On Wed, Oct 14, 202
d, Oct 14, 2020 at 5:25 AM Michaël Rouges <
>> michael.rou...@gmail.com> wrote:
>> >> >>
>> >> >> Sorry but my question isn't about providing a tool to generate our
>> documentations but to have a standard syntax to describe our code
>>
gt;
>> >> Michaël Rouges - https://github.com/Lcfvs - @Lcfvs
>> >>
>> >>
>> >> Le mar. 13 oct. 2020 à 01:29, Jordan Harband a écrit :
>> >>>
>> >>> Hopefully (imo) people are hand-writing more docs now, rather than
>
23 PM #!/JoePea wrote:
> >>>>
> >>>> Why not? People are generating less docs now? That doesn't sound good!
> >>>>
> >>>> #!/JoePea
> >>>>
> >>>> On Mon, Aug 17, 2020 at 4:15 PM Isiah Meadows <
> cont...@isi
e
>>>> > automated docs generation tooling in the JS community. Most the actual
>>>> > use JSDoc provides nowadays is editor autocomplete hints and
>>>> > integrating with TypeScript (in cases where changing the extension
>>>> > i
; > use JSDoc provides nowadays is editor autocomplete hints and
>>> > integrating with TypeScript (in cases where changing the extension
>>> > isn't possible for whatever reason), so while it's still useful, it's
>>> > just not used in the same places it was used
>> > cont...@isiahmeadows.com
>> > www.isiahmeadows.com
>> >
>> > On Sun, Aug 16, 2020 at 6:39 PM Michaël Rouges <
>> michael.rou...@gmail.com> wrote:
>> > >
>> > > Hi all,
>> > >
>> > > Since JSDoc seems
hmeadows.com
> >
> > On Sun, Aug 16, 2020 at 6:39 PM Michaël Rouges
> wrote:
> > >
> > > Hi all,
> > >
> > > Since JSDoc seems cerebrally dead, why the TC39 doesn't make a real
> documentation standard, evolving with the langage?
> > >
> &g
eadows
> cont...@isiahmeadows.com
> www.isiahmeadows.com
>
> On Sun, Aug 16, 2020 at 6:39 PM Michaël Rouges
> wrote:
> >
> > Hi all,
> >
> > Since JSDoc seems cerebrally dead, why the TC39 doesn't make a real
> > documentation standard, evolving wit
Sorry, I should be a few more explicit about the needs, I'll try to fix it.
(Sorry If my english isn't perfect, it isn't my native language)
Ihmo, the developers needs a strong/robust/uniform way to describe their
code, using static types comments and how they are using the language
features,
reason), so while it's still useful, it's
just not used in the same places it was used previously.
-
Isiah Meadows
cont...@isiahmeadows.com
www.isiahmeadows.com
On Sun, Aug 16, 2020 at 6:39 PM Michaël Rouges wrote:
>
> Hi all,
>
> Since JSDoc seems cerebrally dead, why the TC39
It’s close, but not quite the same, from a cursory read. Thanks for sharing
though.
To respond to the original post, I don’t think something rigidly formal would
work out given how many wildly different opinions are out there - thinking out
loud, but perhaps something underlying similar to
> This feels like rich territory for a blog post, if someone feels
qualified? Specifically, just running the typescript tool chain for jsdoc
annotations, which are excellent for all the reasons mentioned above
(comments only, vanilla js etc).
Does this count?
This feels like rich territory for a blog post, if someone feels qualified?
Specifically, just running the typescript tool chain for jsdoc annotations,
which are excellent for all the reasons mentioned above (comments only, vanilla
js etc).
> On 17. Aug 2020, at 19:35, Andrea Giammarchi
>
Sorry, new link:
https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html
On Mon, Aug 17, 2020 at 8:34 PM Andrea Giammarchi <
andrea.giammar...@gmail.com> wrote:
> TS supports JSDocs already
>
>
TS supports JSDocs already
https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html#supported-jsdoc
On Mon, Aug 17, 2020 at 8:31 PM Bergi wrote:
> Hi,
>
> > They don't want to add TS to their stack.
>
> Then what else would they want to add to their stack? Notice one
Hi,
> They don't want to add TS to their stack.
Then what else would they want to add to their stack? Notice one doesn't
necessarily need the TypeScript Compiler to add TypeScript- or Flow-like
type annotations and remove them in a build step - Babel for example
could do that just fine as well.
Hi all,
Since JSDoc seems cerebrally dead, why the TC39 doesn't make a real
documentation standard, evolving with the langage?
Actually, a part of the JS community are exiling to TS to type anything
and the rest are just despited by the very outdated version of JSDoc but
don't want to add TS
19 matches
Mail list logo
