Changes between Version 2 and Version 3 of Ticket #35741


Ignore:
Timestamp:
Sep 7, 2024, 3:59:06 PM (3 months ago)
Author:
Chase Adams
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35741 – Description

    v2 v3  
    4242While OneToOne is not as commonly used as other relations, I believe the verbosity and clunkiness of the current design would benefit from a refresh.
    4343
    44 The main concept I'd suggest for informing a better design would be that both the forward and reverse relations should be symmetrical in usage. In other words, for anything you can do on the forward relationship (checking if it exists, assigning it, etc), the same is possible on the reverse. This would be more implicit with the idea of a "One to One" relationship, where structurally neither model is a parent but instead both models share a peer relationship, and peers should have equal capabilities.
     44The main concept I'd suggest for informing a better design would be that both the forward and reverse relations should be symmetrical in usage. In other words, for anything you can do on the forward relationship (checking if it exists, assigning it, etc), the same is possible on the reverse. This would be more implicit with the idea of a "One to One" relationship, where structurally neither model is a parent but instead both models share a peer relationship, and being peers implies having equal capabilities.
Back to Top