BAH-3854 | AppointmentEventsAdvice should not throw when older validateAndSave is called #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apologies for not creating a ticket; my browser and Atlassian cloud are not working at the moment.
In #117,
AppointmentEventsAdvice
was added to enable publishing events when appointments are created. This advice is bound to thevalidateAndSave()
method onAppointmentService
. Unfortunately, there are twovalidateAndSave()
methods onAppoinmentService
, one which takes aSupplier<Appointment>
and one which just takes an appointment. The advice assumes it is called by the version that takes aSupplier<Appointment>
so that if the other one is called, an exception is thrown, aborting the attempt to save.This PR fixes that by ensuring the advice also works if the first argument is not an appointment. I also added some extra defensive checks to ensure that the
Supplier
returns anAppointment
as expected.