Is the documentation currently maintained/updated?

https://developers.google.com/closure/library/docs/overview
https://google.github.io/closure-library

Is there interest in having a single source of truth that people can point to? There are a few issues open regarding documentation: #968, #963, #856, #861

Here I have another suggestion, this time about our Gravity's CLI. I come up with this list of improvements which I think should benefit the project:

• If no arguments passed it should display help section instead of opening REPL
• To open REPL add a new flag for example gravity --repl
• gravity new [project] - a new simple command to create new project. (A wizard which helps with co

A linter for closure stylesheets could detect a lot of simple style issues like unsorted @requires, whitespace conventions, etc.

Probably there would be some obvious problems to point out globally and some Google style guidelines documented at https://github.com/google/styleguide that could be enabled via a flag.

Javadoc is not yet available online. Add it to a folder in gh-pages:

zbra-solutions.gitub.io/android-linq/JavaDoc/v1.0.X/
zbra-solutions.gitub.io/android-linq/JavaDoc/v1.1.X/

And so on...

Also:

• add Wiki page listing versions and links to their javadocs
• add a direct link from Readme.MD to the latest version
• update website page to according to Readme.MD

Documentation can be combined from multiple sources. Probably the best option atm is to gather type documentation from apiDescriptions.json as most of the hard work is done and it seems to be kept uptodate.

The per function and property documentation could be grabbed from either:

• the closure e

I have found an interesting aspect about MySQL index. When I create a multi column index, the prefix key field length can't be greater than a specified value.

I create a test table s_prefix_index;

create table s_prefix_index(id int, name varchar(1024), age int);

Then I create a multi column index,

mysql> create index `idx_name_age` on s_prefix_index(name, age