aws-amplify / aws-amplify/amplify-studio
m:n relationship adds queries to model
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
n/a
### Region
n/a
### Environment name
n/a
### Figma File Version (if applicable)
_No response_
### Amplify CLI Version
_No response_
### If applicable, what version of Node.js are you using?
_No response_
### What operating system are you using?
_No response_
### Browser type?
_No response_
### Describe the bug

opening an issue from comment https://github.com/aws-amplify/amplify-studio/issues/696#issuecomment-1442465513.
using visual editor to create a m:n relationship in v1 adds`@model(queries: null)` on a model. The visual editor become disabled.
### Expected behavior
not add `@model(queries: null)` if unsupported by visual editor
### Reproduction steps
1. create model in transformer v1 in visual editor
2. create many to many relationship with another model
3. observe visual editor becomes disabled
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start with the visual editor's Transformer v1 model creation flow and reproduce the many-to-many relationship steps described in the issue. Trace where the relationship adds @model(queries: null), then verify that unsupported query settings are not added and that the visual editor remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100