Jack Franklin c6577bae1c Add support for Platform.UIString calls in GRDP parsing ...

Now UIString is defined in Platform [1] we need to update the GRDP
parsing code to look for calls to it rather than `Common.UIString`.

We still support `Common.UIString` so this CL extends the script to look
for:

1) Usage outside of Platform:

```
import * as Platform from '../platform/platform.js';

Platform.UIString.UIString('foobarbaz');
```

2) Usage inside of Platform:
```
import {UIString} from './UIString.js';

UIString('foobarbaz');
```

[1]: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2165793

Change-Id: I8c0f97817709e936bdddce8f0b60d759e80fd1ba
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2170067
Reviewed-by: Paul Lewis <aerotwist@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>

2020-04-28 14:13:33 +00:00

..

tests

Add support for Platform.UIString calls in GRDP parsing

2020-04-28 14:13:33 +00:00

check_localized_strings.js

Add support for Platform.UIString calls in GRDP parsing

2020-04-28 14:13:33 +00:00

localization_utils.js

Add support for Platform.UIString calls in GRDP parsing

2020-04-28 14:13:33 +00:00

md5.js

Run ESLint on the scripts directory

2020-03-11 14:47:51 +00:00

parse_typescript_files.js

Extend GRDP tooling with TypeScript support

2020-03-10 11:50:43 +00:00