You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening openeo.d.ts in VS Code, it displays me "482 problems in this file". I think most (if not all) of them stem from a missing . when specifying types for object keys/values with object<x,y>, because everything is fine until here:
The TS generation is done by the typescript compiler pretty much, the checks might be done by JSDoc and it seem different rules apply. So it probably depends on the installed VS Code extension.
v3.0.0 we could probably implement in typescript to get rid of the issues, but for now it's not a priority as long as TS users get the typing, which I never heard complaints about yet so I assume it works.
Hm okay. I tried a search&replace and indeed that resolved all the 'problems'.
However with some quick googling I couldn't find documentation for neither variant (not with nor without the dot), and all StackOverflow examples were using totally different syntax, so I ended up trying asking Copilot -- here's what it said:
I wouldn't take that as authoritative, but will leave the info here for someone to pick up if this should become a more relevant issue at some point.
When opening
openeo.d.ts
in VS Code, it displays me "482 problems in this file". I think most (if not all) of them stem from a missing.
when specifying types for object keys/values withobject<x,y>
, because everything is fine until here:openeo-js-client/openeo.d.ts
Lines 122 to 131 in 6d0e09b
The JSDoc has the
.
but the actual code doesn't. Do they share the same syntax rules?I'd be happy to go through the file and fix this all over. Just: Where is this file actually used so that I can test the changes?
The text was updated successfully, but these errors were encountered: