Open wxiaoyun opened 3 months ago
Without making contact name and phone number compulsory, our app will no longer be an internship application manager that doubles as an internship contact management app.
Should we do this, we would violate the brownfield constraints by morphing AB3 in a different direction (since it is no longer a contact manager). Thus, it is necessary for us to keep contact name and phone number compulsory.
Team chose [response.Rejected
]
Reason for disagreement: I agree with the team's decision on every other issue I have reported but I am afraid I must insist my position regarding this issue.
I would argue that changing previously compulsory fields to optional field would fall under "evolving/enhancing/morphing the given code base...incrementally", hence it does not violate the brownfield constraint. Furthermore, this change (compulsory -> optional) is already made in my group's TP, so it should be fine.
Also in the UG, CareerSync is stated to be "internship application manager" instead of "contact manager", so I do not exactly follow the "it will no longer be a contact manager" argument made.
Description
CONTACT_NAME
,CONTACT_EMAIL
compulsory can make the app harder to use and potentially less helpful.Steps to reproduce
add /com Netflix /desc test /status to_apply
Expected
Actual
Potential Suggestions
Screenshots