It can be useful to add a toString() and toStringShort() methods for device_info plugin. Instead of getting the fields one by one, we can use these methods for quick information about the device.

DEMO的页面push生硬
建议使用默认的 Navigator.pushName
这么生硬的DEMO很影响Flutter在开发者技术选型时的判断

https://github.com/dart-lang/sdk/blob/master/docs/process/experimental-flags.md#flag-format-for-cli-based-tools

Our docs show:

dart --enable-experiment super-mixins

This format does not work on the VM. It should be:

dart --enable-experiment=super-mixins

Web socket as data Provider

todos_repository_simple explains nicely about the benefits of using repository as singleton. But no where it's mentioned how to handle the web sockets.

How can I use web socket (webSocket and fileStorage) instead of rest (webClient and fileStorage) ?

Some key points between web socket and rest.

• The name itself signify socket

If anyone is interested in contributing to Chinese (Simplified) Docs with me, please let me know, so that we can work together and speed things up! I will mainly follow the order to continue, if you are willing to contributing, you are always welcome to pick up any page you like!

The remaining parts are:

• Tutorials
  • Flutter
    • Counter
    • Timer <-- @jakecast

一个FLBFlutterViewContainer装载多个flutter页面，里面由Flutter Navigator来进行路由管理。
`
@override
Widget build(BuildContext context) {
PushListener listener = new PushListener();
return MaterialApp(
title: 'Flutter Boost example',
builder: FlutterBoost.init(),
navigatorObservers: [listener],
home: Container(),
)

class PushListener extends NavigatorObserver {
@

In the Evaluation doc in wiki, it incorrectly says Maidenhead (mls) can form words. Since MLS alternates pairs of letters and pairs numerals, it could only form EL33tt haxor words, and at least for the experienced user, or with a syntax checking interface, no letter/number ambiguity.

(MLS does have seams between fields and between squares so that adjacent places may be disimilar, but even OL

Casts names are Over lapping with each other when inkino.app website opened in mobile device as desktop site. Attaching a screenshot for reference. I opened the website in Xiaomi Redmi 5A device and chrome as browser running its latest version.
![screenshot_2018-12-29-15-40-28-268_com android chrome](https://user-images.githubusercontent.com/22256553/50548297-2e0d3a00-0c70-11e9-9d3e-0ed66e45ba2a.

Someone else also had this problem when running in the browser and by switching back and forth between tabs, but it is not web specific.

It can easily be reproduced by running docs/example/box2d/contact_callbacks and turn off your device screen or change app, and then go back to the app and the bodies will have less or no momentum.

Vscode handles > in tags by calling html/tag and eventually closing the tag.

Example request:

[Trace - 7:58:44 AM] Sending request 'html/tag - (138)'. Params: { "textDocument": { "uri": "file:///home/kyoncho/Sources/lsp-docker/demo-projects/Scala/hello/src/test/scala/example/foo.html" }, "position": { "line": 0, "character": 6 } }

[Trace - 7:58:44 AM] Received response 'html/tag 

Please rewrite the cloud_firestore library in native dart, so we can remove all the big (in terms of download size) Android and iOS libraries. Which slow down build time dramatically.

Having to create a manual abstraction to support https://pub.dev/packages/firebase and https://pub.dev/packages/cloud_firestore is a mess.

All future platforms would be supported out of the box.

Something l

When releasing a new version it's always hard to deliver a proper changelog. Keep a changelog is a proposal on how we can deliver a consistent and complete changelog.

I propose we implement it in this repo. I would require the following steps:

• Refactor the changelog to the keep a changelog spec.
• Add up

It’s not part of the OAuth spec but in particular we should call out that it takes a JSON body in the template.

The firebase_messaging documentation says:

When sending a notification message to an Android device, you need to make sure to set the click_action property of the message to FLUTTER_NOTIFICATION_CLICK. Otherwise the plugin will be unable to deliver the notification to your app when the users clicks on it in the system tray.

We

Most users only have the capacity to fix deprecation warnings in their own code, but they may end up using libraries that have their own deprecation warnings. We should add a --quiet-upstream flag (and similar flags for the Dart and JS APIs) to silence deprecation warnings emitted by upstream libraries (that is, libraries loaded through load paths and package: URLs).

I think this flag shou