Alexander Harding

Yeah. I think it's OK to keep the objects in the fetchFn for the infinite pagination, but the post component should use data in the redux store as the source...

I would appreciate that. mdast parsing is not my forte.

Okay, thanks @DakshG07! If it helps, my investigations in the past led me to the following info: - Lemmy uses https://github.com/markdown-it/markdown-it-container to parse spoilers. - No perfect alternative for remark.js...

@80avin @DakshG07 I've assigned the two of you, feel free to collaborate and correspond in this issue!

> Oh, and additionally: the spoiler component would also have to implement a click handler similar to `LinkInterceptor`, as currently clicking on it collapses the comment. Yeah. I'm hoping though...

> Out of curiosity, where do you go to write your test posts? I want to do some testing with the spoilers, but I also don't want to create unnecessary...

@LazaroFilm, it boils down to building a plugin that adds support for spoilers via https://github.com/remarkjs/react-markdown. Unfortunately Lemmy's spoiler format is nonstandard markdown. So, this is no easy task. @DakshG07 has...

I looked into this a bit more this weekend. I think we need to go lower level and make a micromark extension, instead of a remark plugin. Then we don't...

Another update, I am currently continuing work on the micromark extension. I made a few attempts at forking learning a bit each time, and the most recent fork is the...

Thanks. We should do something like we do for the new post dialog. But it will require significant refactor to not use the useIonDialog hook (in order to determine whether...