Azure / Azure/data-api-builder

[Known Issue] Relationship name and exposed field name of an entity must not overlap

Ouverte
#1,937 1 commentaire 0 réactions 1 personne assignée Réclamée par @seantleonard Voir sur GitHub
bug config known-issue validation
Langage dominant
C#
Étoiles
1.5k
Forks
370
Merge moyen
3 j 22 h
PR mergées (30 j)
9

Description

note: this is a validation that should be added.

For queries (and later on for nested mutations as well), we don't have a validation in place which ensures that the relationship names and the exposed column names which belong to a particular entity (table) do not conflict with each other. In current situation, if we give same names for a relationship and an exposed column name, the engine would crash. This might be a GQL only validation since for GQL queries/mutations, relationship fields and column fields are combined. Need to evaluate where and when the validation should occur.

In the below example, there is a column named `title` in the `Book` entity and a relationship by the same name as well.
image

---------------------

image

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.