In hosting/surfing/event references, the person who left the reference's profile photo, name and age are shown along with their current location rather than the place where the person hosted or surfed.
We should be storing the place where the person was hosted/surfed/event took place. This adds important context if the person fails to mention it in their reference - especially if the person is referring to the person's living situation in their reference.
See example of what is (incorrectly) happening right now:
In the example above, instead of "Berlin, Germany" it should say, "Host in Madison, USA". If it were a surfing reference, it should say "Guest in Madison, USA".
I suspect this will require a backend update (store the location of the request at the time of request, eg. HostRequestLocation) and then a frontend update so that we are displaying the location that the hosting/surfing happened.
In hosting/surfing/event references, the person who left the reference's profile photo, name and age are shown along with their current location rather than the place where the person hosted or surfed.
We should be storing the place where the person was hosted/surfed/event took place. This adds important context if the person fails to mention it in their reference - especially if the person is referring to the person's living situation in their reference.
See example of what is (incorrectly) happening right now:
In the example above, instead of "Berlin, Germany" it should say, "Host in Madison, USA". If it were a surfing reference, it should say "Guest in Madison, USA".
I suspect this will require a backend update (store the location of the request at the time of request, eg. HostRequestLocation) and then a frontend update so that we are displaying the location that the hosting/surfing happened.