Dennis Hackethal

Something like `post.versions` would be fine. It could return an array with the original as the first element and then all subsequent versions in the order they were created. I...

That all sounds good to me. I vote calling it `logidze_versions` instead of disabling it by default. You can always just do ```ruby def arbitrary_versions_attr logidze_versions end ``` and so...

I can reproduce the first issue: ```html foo ``` is converted to: ``` 1. foo === ``` Which a markdown parser (I'm using [this one](https://daringfireball.net/projects/markdown/dingus)) turns into: ```html foo ===...

Here's a workaround for the consumer side to fix the first issue for now. I created it with the help of AI and only lightly tested it. I'm a Turndown...

Disregard [previous workaround](https://github.com/mixmark-io/turndown/issues/357#issuecomment-1694734736) in favor of this fix as per my PR #447: ```js rules.listItem = { filter: 'li', replacement: function (content, node, options) { content = content .replace(/^\n+/, '')...

I think it's a good call to use a BehaviorSubject here, but what I'm saying is that its initial value is wrong if the page is opened with query params,...

Let me get right on that.

Not a fan of Plunkr, but here it is in a repository: https://github.com/dchacke/angular-2-query-params-bug Should be simple to start up. Instructions on how to reproduce the bug are in the Readme.

And here's what I did to cause the issue: https://github.com/dchacke/angular-2-query-params-bug/commit/0c047c7e4bd52bc5bc06fb006c628b55b8fd0bad

`skip(1)` will not work for reasons described above, because I will not be able to capture when the user is actually on a page with no query params. The subscription...