| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Analogous to what the 'compat/compat' rule indicates already, and the
fact that CI, fresh-node, and local dev generally involves recent
versions of Firefox, Chromium-based browsers, or Safari.
This patch is a minimal first step that only loosens the linter,
and auto-fixing only unusual cases where a new rule specifically
warned against existing code.
Change-Id: Ic64f650bd64669c57b884de3f75b23f3549b0c9f
|
|
|
|
|
|
|
|
| |
The doc folder contains (committed) json files with schema definition
for json files
That should be linted as well to spot syntax errors easier
Change-Id: I20ff7abf6b98d2247ee52e2d2b43af88c062f779
|
|
|
|
|
|
| |
The {en,qqq}.json syntax is Grunt-style, not eslint-style
Change-Id: Ie05358cd17232079857d349ac310751ed637b2a6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A `SettingsSource` is meant to represent any kind of local or remote
store from which settings can be read, be this a local file, remote URL,
database, etc. It is concerned with reading in (and possibly decoding)
settings data, and computing a consistent hash key that may be used in
caching.
A `SettingsFormat` is meant to detect supported file types and/or decode
source contents into settings arrays. As of now, JSON is the only
supported format but others may be implemented.
`FileSource` is the first source implementation, with its default format
being JSON, meant to read settings from local JSON files.
`ArraySource` is mostly useful for testing using array literals.
Refactored `SettingsBuilder` methods to use the new source abstractions.
Bug: T295499
Change-Id: If7869609c4ad1ccd0894d5ba358f885007168972
|
|
|
|
|
| |
Bug: T291674
Change-Id: I0d0b78d59a02023b97249c116d8754ad9d4be5e0
|
|
|
|
|
|
|
|
| |
* Move data files to /data
* Add benchmarkCommentFormatter, named for the new class hierarchy.
Bug: T285917
Change-Id: Idf2529894fe63d34087d6d5ce4dd1676c89b1373
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds the MDN polyfills for Array.prototype.find, findIndex, and
includes to core, along with a skip function. Polyfills live a
single "es6-polyfills" module in case additional similar polyfills
need to be introduced in the future.
Introducing these in core will allow certain extensions
to stop shipping local copies.
Bug: T264135
Change-Id: I37953f6fcad693a8d25e1a19764abd55bbbbb242
|
|
|
|
| |
Change-Id: I493af7938eaa744a9e869e611f54de5cbaa2692e
|
|
|
|
|
| |
Bug: T276477
Change-Id: Ic1e3c4b00f3a3319f032620f9c96cafd3ee174ad
|
|
Note that node_modules is excluded by default.
Bug: T249858
Change-Id: Iaa69092b11e49ebf9cc5f2ec8a695894cda31b83
|