Assigned
Status Update
Comments
jk...@google.com <jk...@google.com>
ma...@gmail.com <ma...@gmail.com> #2
Any word on this?
de...@iboapp.info <de...@iboapp.info> #3
I suppose as long as the workarounds with API library project work, there will be no need to improve it. see https://plus.google.com/104403800912062884925/posts/H75XFQxtHkc
ca...@gmail.com <ca...@gmail.com> #4
I was reading this article : https://developers.google.com/closure/compiler/docs/js-for-compiler
Yet I couldn't document my "enums" with @enum. I guess this is the same issue. Only the first level functions seem to be documented properly.
Yet I couldn't document my "enums" with @enum. I guess this is the same issue. Only the first level functions seem to be documented properly.
zi...@zizix.org <zi...@zizix.org> #6
this problem hinders the development of GAS in the direction of user libraries.
[Deleted User] <[Deleted User]> #7
Checking in on this item. This would be an amazingly helpful functionality and assist greatly in efforts to generate open-source libraries that instantiate classes.
[Deleted User] <[Deleted User]> #8
very interested in this as well. Please help Google!!! You're our only hope!! ...oh yeah and update to ECMA 6
D:
Thanks :D
D:
Thanks :D
[Deleted User] <[Deleted User]> #9
+1
jo...@gmail.com <jo...@gmail.com> #10
+1
ma...@gmail.com <ma...@gmail.com> #11
I hope the one issue blocking this is to convert the thinking at Google to more of a predictable, typed paradigm - and I hope it happens soon!
ma...@bkper.com <ma...@bkper.com> #12
Hi guys,
If you are working with TypeScript, we've built a package that aims solve this:
https://github.com/maelcaldas/clasp-types
We use it internally to generate autocomplete for OO libraries and Client-side API written on Typescript.
Happy to have your feedbacks on that.
If you are working with TypeScript, we've built a package that aims solve this:
We use it internally to generate autocomplete for OO libraries and Client-side API written on Typescript.
Happy to have your feedbacks on that.
[Deleted User] <[Deleted User]> #13
+1
jo...@appier.com <jo...@appier.com> #14
+1
je...@dp6.com.br <je...@dp6.com.br> #15
+1
pr...@gmail.com <pr...@gmail.com> #16
+1
bo...@gmail.com <bo...@gmail.com> #17
+1
an...@google.com <an...@google.com> #18
Hi there!
I've made a new internal report. If we have any updates or inquiries, we'll post them here.
Cheers!
[Deleted User] <[Deleted User]> #19
+1 here, in case we get any updates on that :)
gi...@gmail.com <gi...@gmail.com> #20
+1 here too
is...@google.com <is...@google.com>
ra...@cloudgarden.pl <ra...@cloudgarden.pl> #21
+1
jo...@campusinternationalschool.org <jo...@campusinternationalschool.org> #22
+1
w4...@gmail.com <w4...@gmail.com> #23
Comment has been deleted.
al...@gmail.com <al...@gmail.com> #24
+1
al...@lyft.com <al...@lyft.com> #25
+1
he...@gmail.com <he...@gmail.com> #26
+1
ze...@gmail.com <ze...@gmail.com> #27
+1
[Deleted User] <[Deleted User]> #28
+1
mm...@gmail.com <mm...@gmail.com> #29
+1
ab...@gmail.com <ab...@gmail.com> #30
This is very important when sharing the AppScript code as library. Easy Documentation should be available for Object Oriented Interfaces e.g.
var a= function(){
//need to share the documentations for using this function when sharing library
this.action=function(){
}
}
var a= function(){
//need to share the documentations for using this function when sharing library
this.action=function(){
}
}
tg...@gmail.com <tg...@gmail.com> #31
11 years...
shame on google
shame on google
jp...@google.com <jp...@google.com>
dr...@gmail.com <dr...@gmail.com> #32
+1
kr...@gmail.com <kr...@gmail.com> #33
+1
vi...@gmail.com <vi...@gmail.com> #34
+1
do...@luxemporiumusa.com <do...@luxemporiumusa.com> #35
+1
an...@gmail.com <an...@gmail.com> #36
Might as well get the autocomplete supported without even the JSDoc as it added new learning curve and lengthened development time. In-depth JSDoc auto-complete support offers little value in return -- more work for both Google and the app script developers.
ri...@gmail.com <ri...@gmail.com> #37
+1
Any update here?
Its very confusing if the library just store all the function name.
Any update here?
Its very confusing if the library just store all the function name.
Description
Currently Google Apps Scripts uses JSDoc on Apps Script Libraries to auto-complete functions on the top of the library.
Still there's no way to document namespaced functions or classes. Only the top level functions will auto-complete.
Notes:
More Info: