maps3d types are outdated

[briancarbone]

defaultUIHidden and mode, at the very least, are not reflected in the current types. defaultLabelsDisabled is still offered, but no longer exists.

[usefulthink]

Yes, that is true. But it's also not an issue of this library.
There are several open issues about that here: https://issuetracker.google.com/issues?q=status:open%20componentid:188853%20@types%2Fgoogle.maps and upvoting those can't be a bad idea.
I know that updated type definitions are being worked on, but I can't say when they will get published.

In the meantime, what I do is create my own types with only the newer stuff I need typed correctly.
For an example, see here: https://github.com/usefulthink/react-google-maps/blob/feat/internal-usage-attribution-ids/types/google.maps.d.ts

The steps for this are:

• create a file ./types/google.maps.d.ts in your project
• at the top of that file, add a directive /// <reference path="../node_modules/@types/google.maps/index.d.ts" /> to load the original outdated types
• add augmented types in a declare namespace google.maps { ... } block
• in your tsconfig, make sure that the new file is part of the typeRoots, so for example: "typeRoots": ["./types", "./node_modules/@types"] (also note the second path, which is required for types from npm to work)

that way the file should be picked up automatically and types declared there will augment the original types from @types/google.maps

This should be a (mostly) correct implementation of all maps3d types: https://gist.github.com/usefulthink/468fd40f224dfbbadfb495d6963783db

[naquiroz]

Hi @usefulthink . A couple more types are not updated too, for instance, the Routes library only has the legacy types.