Praanesh S

Hey, we can set custom names for each table in Hasura. BUt, if we do this directly in the console, we have to manually rename them with every deployment to...

Hey, Actually I found that configuration files under the `graphql` directory. I think we can setup custom names over here for each table. Maybe I will try that.

Hey @Naramsim, I’ve set up the Dev Container for the project, check it out when you have a moment. If it looks good, I’ll add the setup instructions. Should I...

Hey, I will work on fixing these issues. After that, we can decide whether to keep or remove the devcontainer based on what works best.

@Naramsim I have fixed the issues and added instructions in the CONTIRUBTING.md. Do check it out and tell me if you face any issues.

Hey, I have few queries: - There was no configuration file found for `pokemon_v2_typesprites`. Was it left out intentionally? - Since I have set up these custom names, the old...

Hey! Hasura's `custom_name` works by replacing the default GraphQL name. It doesn't create an alias or expose both the original `pokemon_v2_tablename` and the `tablename` simulltaneously. So, I think It is...

I have another query regarding how a "v2 to v3" API transition will affect our database tables. Would it involve renaming all existing tables, for example, from `pokemon_v2_move` to `pokemon_v3_move`?...

Hey @Naramsim, If we want to support both for limited time, we can do it by - **Option 1**: Keep the existing Hasura instance from the master branch (with the...

Hey @Naramsim, I updated the branch with these changes: 1. Indentation is fixed. 2. `pokemonV2` prefixes are removed. 3. The `typesprites` table is now tracked. I have also force-pushed this...