-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Closed
Labels
DataStoreRelated to DataStore categoryRelated to DataStore categorybugSomething isn't workingSomething isn't working
Description
Before opening, please confirm:
- I have searched for duplicate or closed issues and discussions.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
JavaScript Framework
Not applicable
Amplify APIs
DataStore
Amplify Categories
api
Environment information
# Put output below this line
Describe the bug
I'm not sure what version/flags of the CLI is necessary to create this scenario. But, I have an "old" sample app wherein the FK fields from some connected models are not available for in the GQL sync query selection set.
I have a Blog
model where I can provide a blogOwnerId
at mutation time:
However, blogOwnerId
is not available in the selection set.
When I add a syncExpression
on Blog
, blogOwnerId
is included to the selection set on sync, and the sync therefore fails.
Expected behavior
DataStore should only include these connection/FK fields in the selection set if they're explicitly defined.
Reproduction steps
🤷
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
Metadata
Metadata
Assignees
Labels
DataStoreRelated to DataStore categoryRelated to DataStore categorybugSomething isn't workingSomething isn't working