Find the booking_id, the correct resolution, fire up postman and 💥
ssh...sudo su deploycd /app/<appname>/current/bin/rails c
Doing a code read today in our monthly 10% time I started to read and document an internal event sourcing framework
we've built in our team. I stumbled across the .dup method and so naturally I got sidetracked (losing sight of the high level) with StackOverflow posts, Ruby-Doc and my own IRB comparisons between it, and another method that appears quite
similar -clone.
Importantly dup differs from clone in that it duplicates the object as a completely new record (if it's an ActiveRecord
object no id is assigned however if it's a PORO a new object_id is assigned so it's completely different).
The duped object has no direct assocation with the original at all. Thus, if you modify a duped object, you won't change
the original object and that's because it's a “shallow” copy – it copies the object’s attributes only, not its associations.
Nightly rates live in the provider_reservation_successful event.
event.event_type = booking_change_creation_failedLook for the reservation or booking using the EAN itinerary ID (not our confirmation number).
In a separate tab run tail -f log/*.log and clear the screen.
Run the specs and see the logs yo. It's HELPFUL!!!
/hotels/bookings/agg-idjson renderered logsI hereby claim:
To claim this, I am signing this object:
rails c of the app in question (the former is the most advisable).reprocess helper method can simply take the aggregate as the arg like so: reprocess(aggregate_id)
|sudo su deploy, cd/app_name/current etc.