fix: applicant split in edit mode, drop create-mode agency checks
This commit is contained in:
1 parent
ad6e42ab0c
commit
38f0f23ea3
12 files changed
+167
-68
No files matched your search
@@ -12,14 +12,14 @@ use App\Form\Service\Contract\FieldConditionInterface;
|
||||
*
|
||||
* It fires only where participant[0] IS the booking's applicant, which
|
||||
* BookingDto::isFirstParticipantApplicant() decides: the booking-level choice in create mode,
|
||||
* and anmelder vs. participant[0] person id in edit mode. Internal agency bookings answer
|
||||
* false there, which preserves the behaviour this class used to spell out itself.
|
||||
* and anmelder vs. participant[0] person id in edit mode, where internal agency bookings
|
||||
* always answer false.
|
||||
*
|
||||
* Business Rules:
|
||||
* - CREATE mode (anonymous user): First participant data is editable (user must fill it in)
|
||||
* - CREATE mode (logged-in, participant[0] is the applicant): data is prepopulated, read-only
|
||||
* - CREATE mode (applicant does not travel, or internal agency): participant[0] is an ordinary
|
||||
* traveller, data is editable
|
||||
* - CREATE mode (applicant does not travel): participant[0] is an ordinary traveller, data is
|
||||
* editable
|
||||
* - EDIT mode (participant[0] is the applicant): always read-only
|
||||
* - EDIT mode (split booking, or internal agency): participant[0] ≠ applicant, editable here
|
||||
* (PersonalDataMutabilityCondition still applies separately)
|
||||
|
||||
Reference in new issue
Block a user