Jonas Finnemann Jensen

For a long list of recent markdown enhancements on GitHub, see: https://github.blog/changelog/label/markdown/

GitLab also has some documentation on markdown: https://docs.gitlab.com/ee/development/gitlab_flavored_markdown/specification_guide/ Notably, they appear to have the same issues finding an up-to-date GFM specification. Regarding footnotes, I'd suggest upvoting issues like: https://github.com/github/cmark-gfm/issues/270 If...

> Changing hosts should not lead to version changes, unless the previous ref cannot be resolved in the new host. I wouldn't expect to have an upgrade behavior when I...

Please upvote this issue, if this is important. IMO, proper mirror support needs to be able to prove that the mirror produces the same resolutions as the mirrored package repository.

For anyone looking to work around this issue the following code-snippet should do: ```js // This ensures that we restore state when user exits fullscreen using escape if (!window._gdjsFullScreenPatch) {...

Yeah, it's probably not a huge issue. The fact that the token is short-lived, makes it a lot better than the hardcoded coveralls-token. But in general it seems unwise to...

> I think...if we want to support arbitrary tools reading pubspec, we should namespace things by the package name. Yes, But also as @sigurdm says `pubspec.yaml` has an open-ended design....

**Disclaimer:** I don't have fully formed thoughts here. > Flutter is doing that for years. I'm just following de-facto standards. Yeah, and `pubspec.yaml` was designed with this in mind. Just...

> the package that reads the config (`jaspr_lints`) is going to be an analyzer plugin and has a different name as the configuration property (`jaspr`) If `jaspr_lints` read from `config.jaspr`...

> `jaspr_lints` reads from `jaspr`. I don't plan to move away from the top-level key. There is no harm from it either, `jaspr` isn't going to conflict with any feature...