| commit | 6edf3560b20e9750c25cf1f24d03ef473b4b5e1e | [log] [tgz] |
|---|---|---|
| author | Ian McKellar <ianloic@google.com> | Wed Jul 20 15:15:11 2016 |
| committer | Ian McKellar <ianloic@google.com> | Wed Jul 20 15:15:11 2016 |
| tree | bf590200cdc86c8d5328f15052631b5d84a9f043 | |
| parent | ecf86ab980592c3095cbd9f0058133e0499d9ad6 [diff] |
Check dart sources with --fatal-lints --fatal-hints Fixes #804 Downstream projects (Flutter, etc) use stricter checking than Mojo traditionally has. The most visible impact of this has been that generated .mojom.dart files have introducted analyzer errors. This change makes the `mojo/tools/mojob.py test` dart analysis phase treat lints and hints as fatal. On top of that it corrects various code conform to this higher standart and modifies the dart bindings generator to comply too. Most of the changes seem harmless, a few could be correcting subtle errors. R=zra@google.com Review URL: https://codereview.chromium.org/2149533004 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 54766d900eba8e1737bf3e7ddf8470ab4079bc1c
The Mojo Public API is a binary stable API to the Mojo system.
It consists of support for a number of programming languages (with a directory for each support language), some “build” tools and build-time requirements, and interface definitions for Mojo services (specified using an IDL).
Note that there are various subdirectories named tests/. These contain tests of the code in the enclosing directory, and are not meant for use by Mojo applications.
The c/, cpp/, js/ subdirectories define the API for C, C++, and JavaScript, respectively.
The basic principle for these directories is that they consist of the source files that one needs at build/deployment/run time (as appropriate for the language), organized in a natural way for the particular language.
The interfaces/ subdirectory contains Mojo IDL (a.k.a. .mojom) descriptions of standard Mojo services.
The platform/ subdirectory contains any build-time requirements (e.g., static libraries) that may be needed to produce a Mojo application for certain platforms, such as a native shared library or as a NaCl binary.
The tools/ subdirectory contains tools that are useful/necessary at build/deployment time. These tools may be needed (as a practical necessity) to use the API in any given language, e.g., to generate bindings from Mojo IDL files.