Open Dangabit opened 1 year ago
Firstly, we should allow for two plane models with the same names, otherwise, this will be a significant feature flaw. Then the question is how to distinguish the two. Users could either use (1) the index of the plane, which is a unique identifier, or (2) the age of the plane, which is also unique in our program, just for the sake of distinguishing between planes with the same name.
Secondly, the root problem for this issue is that we only want to support so many characteristics of a plane. Currently, there are only two, so it's harder to distinguish. As we add more fields later on, this problem would be solved.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
I have 2 planes with model "abc". However, if I were to unlink the plane, I need to remember which of the index I used to link it.
With more planes added, this can be a huge problem.