Rich message rendering #24

I don't know tbh, someone smarter look at this.

This adds support for rendering rich messages and creates what I think is a good way to handle events. This still needs work and even if we decide not to use this someone else can probably reuse code from this

I don't know tbh, someone smarter look at this. This adds support for rendering rich messages and creates what I think is a good way to handle events. This still needs work and even if we decide not to use this someone else can probably reuse code from this

Just going through a visual analysis of your code, I'll test it and give a full review in the future.

To consider: highlight.js is thicc. It's almost 1MiB. Not sure if bundle size is something we care about but we should probably keep this in mind...

1 MB bundle size is kind of ridiculous. We could simply not highlight code blocks, or we could maybe inline async import the module on demand when we actually need to do highlighting, so it's out of the initial bundle.

Added lazy loading for highlight.js. It's a bit hacky and uses an eval() but it gets the job done

 @ -0,0 +50,4 @@
 	}
 }
 function simpleEvent(filter, render) {

 @ -0,0 +3,4 @@
 const UnknownMembership = simpleEvent((e) => e.type == "m.room.member", (e) => "unknown membership event")
 function createMembershipEvent(membership, message) {
 	return simpleEvent((e) => e.type == "m.room.member" && e.content.membership === membership, message)

 @ -0,0 +25,4 @@
 	}
 })
 //Handle our custom tag

Labels Milestones

Rich message rendering #24

Reviewers

Step 1:

Step 2:

 @ -0,0 +13,4 @@
 	// predicates
 	canGroup() {