Some types are shown as unresolved in my GAS project unexpectedly #1005
Unanswered
EmilyGraceSeville7cf
asked this question in
Q&A
Replies: 1 comment
-
I found that the file containing the JSDoc has to be open in an editor tab for it to be parsed. If there is a way around this so the whole project is automatically parsed I would like to know. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Here is my project. Sometimes when I hover on types defined in types/.js files as JSDoc comments I get / unresolved */ warning from intellisence. Why it happens and how to fix it?
Open original question
Beta Was this translation helpful? Give feedback.
All reactions