Azure / Azure/data-api-builder

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

オープン
#1,937 コメント 1 件 リアクション 0 件 担当者 1 名 @seantleonard が担当を希望しています GitHub で見る
bug config known-issue validation
主要言語
C#
スター
1.5k
フォーク
370
平均マージ
3日 22時間
マージ済み PR(30日)
9

説明

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

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。