Ham Vocke
Ham Vocke
Over at Stack Exchange we're seeing an issue with Markdig's link detection within pipe tables (example post [here](https://meta.stackexchange.com/a/357189/507720) for the curious). I think it breaks down to Markdig's `LinkHelper` detecting...
I found another aspect where the pipe tables extension is doing things differently than what GitHub-flavored Markdown suggests. While we're at it, maybe we can get another tweak in for...
One more deviation from the GitHub-flavored markdown specification. Again, I'm happy to put some work into this to make markdig more compliant to the GFM specification but with this one...
I'm working with markdig's Pipe Tables Extension and found a case where the [specified behavior around normalization](https://github.com/lunet-io/markdig/blob/master/src/Markdig.Tests/Specs/PipeTableSpecs.md) is different from what [GitHub-flavored Markdown](https://github.github.com/gfm/#example-204) is specifying. GFM says: > The remainder...
I've started building an autocomplete component that can be used for type-ahead search, e.g. for searching tags, users or anything else, really. This is still a work in progress but...
When I open an active build step's output there's a good chance that more output keeps coming in. The show output layer scrolls to bottom automatically which is quite annoying...
Currently the AI plays random valid cards. This is the most trivial, non-predictable implementation but of course doesn't make sense for anyone seeking real fun and a challenging game. We...
I **really** want this game to be playable by everyone who wants to play it, regardless of disabilities or other limitations. One of the things we can do to improve...
See #7: the notification bar is spamable to so other content is seeable. Limiting it to 1 seems reasonable because right now i cant think for a moment to display...