STOP GENERATING THOUSANDS OF MODULES!!! about elixir-google-api HOT 7 OPEN

I ended up ditching this library in favour of directly working with the API I needed, it worked much better.

from elixir-google-api.

I experimented with this. Kind of a thought-stream as I went. But not generating a module per Model/schema seems like good bang for the buck: https://fosstodon.org/@lawik/111306047662675335

(github branch ref for ease: https://github.com/lawik/elixir-google-api/tree/lightweight-generator)

Instead of modules and structs it will generate a bunch of functions and it will provide typespecs for the non-struct maps. So you still get t docs in iex and can know what type goes where.

For a fairly small API with a bunch of Models (Chat API V1) it went from 101 modules to 5.

from elixir-google-api.

Is there a plan to fix this? I'm thinking I'm just going to vendor the modules I need instead of including the full library but it feels dirty.

from elixir-google-api.

I've just always brought in only the sub-repos necessary (e.g. google_api_storage only results in GoogleApi.Gax and GoogleApi.Storage), or is there a cost I'm not noticing?

I can definitely see not wanting "everything" if you're pulling in the "root" repo though. That could be annoying. This whole repo at large feels abandoned though.

from elixir-google-api.

If I generate just the AiPlatform endpoints of Google which would be one of these deps. That is about a thousand modules in schemas/models. Most of which I don't use or need. Thousand modules takes a bit to compile.

from elixir-google-api.

Ah dang, that stinks

from elixir-google-api.

If mix doesn't support explicitly include/excluding modules it probably should and would be a good feature to suggest in its issues.

This made me realize we should have include support in rebar3/relx :). reltool supports explicit include but in rebar3/relx we only support exclude which probably isn't good enough in this situation since you'd have to list so many.

from elixir-google-api.