search

scaphold-io / scaphold-issues

Post issues that you find on Scaphold here. Post anything about the platform, docs, boilerplates, etc... Happy Scapholding!
3 stars 0 forks source link

duplicate fields when renaming connections #9

Open brandonmp opened 7 years ago

brandonmp commented 7 years ago

I have a 1:M connection between type User (1) (field: invitations) and type Invitation (many) (field: sender)

If I:

  1. edit the sender field on Invitation, and

  2. rename the remote reverse field name from there (i.e., from invitations to invitationsSent),

the User type now has fields for both invitations and invitationsSent

looks like a bug, though it's easy enough to work around since these types don't have any records yet

note that deleting invitations from User in this instance resulted in the Invitation field sender being deleted, so invitationsSent remains as an orphan connection field

mikeparisstuff commented 7 years ago

I will look into this. There is a lot going on behind the scenes with connection fields so I will try to repro and get a fix in asap.