Jonas Finnemann Jensen
Jonas Finnemann Jensen
Looks like [tool/update-gh-pages.sh](https://github.com/dart-lang/markdown/blob/f6eaea38146d8901756418c4e7123eb7bd77249e/tool/update-gh-pages.sh) can be used to generate `gh-pages` which creates the website: https://dart-lang.github.io/markdown/ It'd be nice if we could configure Github Actions to automatically update the site, either: *...
Proposal: If you've published more than 5 versions over the past 30 days, then publishing validations throw an error. This can be ignored with `--skio-validation`. We can fetch versions from...
There is a JSON schema here: https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/pubspec.json However, it has some bugs, for example on `publish_to: none`, because it uses `oneOf` instead of using `anyOf`. I think we should fix...
Hmm, not sure I might have a SASS formatter that took some liberties :see_no_evil: I can look into fixing that sometime -- or we can consider adopting something like it...
By default we limit packages to publishing at-most 1000 package versions. This aims to: * Keep the size of the version listing API end-point reasonable (which would otherwise slow down...
We might be wise to wrap email sending in an zone that handles unhandled exceptions, then close the `PersistentConnection` and avoid reusing it.
Can't publish if `test/testdata/foo.dart` imports `package:example/`. This fails due to: [`validator/strict_dependencies.dart`](https://github.com/dart-lang/pub/blob/d86e3c979a3889fed61b68dae9f9156d0891704d/lib/src/validator/strict_dependencies.dart) We need a way to include arbitrary test data, perhaps we could: * Have a mechanism to opt-out of...
Should we use: `content-transfer-encoding quoted-printable` Are we use using any encoding :D
The [documentation page for pubspec](https://github.com/dart-lang/site-www/blob/1f27503b89a57d3bc50c96cd625d4e742f5c1435/src/tools/pub/pubspec.md#supported-fields) states that additional top-level fields are ignored. A recent analysis of all pubspecs from packages published on `pub.dartlang.org` suggests that many custom properties are unintended...
## Ultimate problem: `schemaPath` and `instancePath` on `ValidationError` is never `null`, so users shouldn't need to check for `null`. ## How it was fixed: `schemaPath` and `instancePath` was made non-nullable....