customising graphql typename generation per source

[0x777]

Currently a source's name is not used in the GraphQL types that we generate. So if two sources have same table names, they can't both be tracked because of type and field conflicts. One can work around this to some extent by customizing each of the table names that cause the conflict. However, it would be very convenient to have this configured per source. We add customization field to the *_add_source API with the following spec:

customization:
  # if root_fields.namespace is absent, the fields
  # are merged into the query root directly
  root_fields:
    namespace: "something"
    prefix: some_prefix
    suffix: some_suffix
  type_names:
    prefix: some_prefix
    suffix: some_suffix

[motleydev]

Another vote for this feature, or more largely described as namespacing sources. Multiple sources is a key part of the Hasura story and adding a configurable guard for field collisions would be useful!

[0x777]

@dmoverton A source offers some schema customization options under configuration section (custom_name, custom_field_names etc), so let's add these fields to configuration section instead of creating a new customization section.

[dmoverton]

@dmoverton A source offers some schema customization options under configuration section (custom_name, custom_field_names etc), so let's add these fields to configuration section instead of creating a new customization section.

@0x777 the *_add_source APIs don't currently have any customization options. The options you mention are only available for an individual table when calling *_track_table. The configuration section in *_add_table is backend-specific, i.e. the structure is different for Postgres, MSSQL Server, etc. The new customization options don't need to be backend-specific which is why I put them in a new section. This is what makes sense in the code. However, if you think it makes more sense in the API to have these under configuration I can do that.

[0x777]

The options you mention are only available for an individual table when calling *_track_table

Ah, right. Sorry, my bad. You can ignore my previous message.

[plcplc]

Closing this issue, as the PR has been merged.

[cleivson]

Closing this issue, as the PR has been merged.

What was the PR that solved this issue? Could you point to the version it was released? Thanks