chrome.gcm method signatures are very, very unreadable

[rdcronin]

The generated signature for chrome.gcm.register is extremely unreadable.

I suspect that this is because the signature takes in a single argument, an array with at least one element and no more than 100 elements:

https://source.chromium.org/chromium/chromium/src/+/main:chrome/common/extensions/api/gcm.json;l=20-31;drc=2857c6b778eb16623281c8e1206ad85baa63cedd

It looks like maybe we're then trying to generate each possible signature? (array of length one, array of length two, array of length three..., array of length 100).

If this is what's going on, it doesn't scale. It's an issue in chrome.gcm, and it would also be an issue with any API where there are multiple arguments (since then you have combinatorial signatures).

Instead of this, could we add a tag to the argument indicating the min / max length?

[AaronForinton]

Hi there @rdcronin and thanks for submitting your issue.

Since this issue relates to Chromium rather than our documentation base, please submit it at https://crbug.com/. Thank you.

[rdcronin]

@AaronForinton This isn't a bug in Chromium. The signature in Chromium is accurate; the method can take an array with a list of strings, and that list must have 100 or fewer elements. It is properly implemented and specified in the schema file, but the files generated for the documentation site represent it by generating every possible signature. We should change that so that it doesn't output every possible signature, but rather that it takes an array of strings with a maximum length of 100.