Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Allow primary field declarations on one-many #2796

Merged
merged 3 commits into from
Jun 28, 2024

Conversation

AndrewSisley
Copy link
Contributor

@AndrewSisley AndrewSisley commented Jun 28, 2024

Relevant issue(s)

Resolves #961

Description

Allows primary field declarations on one side of one-many.

Declaring it as primary doesn't do anything, but there is no reason it shouldn't be permitted and it definitely shouldn't have errored the way it did.

@AndrewSisley AndrewSisley added bug Something isn't working area/schema Related to the schema system labels Jun 28, 2024
@AndrewSisley AndrewSisley added this to the DefraDB v0.12 milestone Jun 28, 2024
@AndrewSisley AndrewSisley requested a review from a team June 28, 2024 16:15
@AndrewSisley AndrewSisley self-assigned this Jun 28, 2024
Copy link

codecov bot commented Jun 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.84%. Comparing base (2aba842) to head (01caa85).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #2796      +/-   ##
===========================================
+ Coverage    78.81%   78.84%   +0.03%     
===========================================
  Files          315      315              
  Lines        23835    23836       +1     
===========================================
+ Hits         18784    18793       +9     
+ Misses        3674     3669       -5     
+ Partials      1377     1374       -3     
Flag Coverage Δ
all-tests 78.84% <100.00%> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
internal/request/graphql/schema/collection.go 90.35% <100.00%> (+0.02%) ⬆️

... and 11 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2aba842...01caa85. Read the comment docs.

@AndrewSisley AndrewSisley force-pushed the 961-one-many-primary branch from 71231f1 to 0015887 Compare June 28, 2024 16:43
Copy link
Collaborator

@fredcarle fredcarle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Unrelated to this PR and spotted by Fred, but it wont get fixed for a while if it doesn't get snuck in here
@AndrewSisley AndrewSisley force-pushed the 961-one-many-primary branch from 958a33a to 01caa85 Compare June 28, 2024 17:10
AndrewSisley added a commit to AndrewSisley/defradb that referenced this pull request Jun 28, 2024
@AndrewSisley AndrewSisley merged commit e5ff02c into sourcenetwork:develop Jun 28, 2024
38 of 39 checks passed
@AndrewSisley AndrewSisley deleted the 961-one-many-primary branch June 28, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/schema Related to the schema system bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@primary directive for 1-Many Fields throws odd error
2 participants