Azure / Azure/data-api-builder

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

Open
#1,937 1 comment 0 reactions 1 assignee Claimed by @seantleonard View on GitHub
bug config known-issue validation
Dominant language
C#
Stars
1.5k
Forks
370
Avg merge
3d 17h
Merged PRs (30d)
8

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.