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.
Converts an m.location event to a map link in order to bridge it to signal. Let's you choose the map provider via config setting.
I ran into a bit of a problem with the different fields that provide additional information.
content.body
is supposed to be able to contain a description. Element just copies thecontent.geo_uri
field there, which isn't adding anything of value, so it shouldn't be printed.content.body
also contains relay sender information after the relay format is applied, so I can't exclude the field. I opted for removing the contents ofgeo_uri
frombody
before prepending it, since that seemed to be the solution with the least amount of change.This doesn't include msc3488. I'm not really sure how to account for that because I still need
body
in relay mode. But maybe we can worry about that when extensible events are out, since those would probably require changes toPortal.apply_relay_message_format
anyway.