Fix up import paths and groups in new TypeScript code.
Review Request #13171 — Created Aug. 1, 2023 and submitted
As we've defined how our JS codebase is going to work going forward,
we've not been terribly disciplined about how we do imports. This change
makes everything consistent with three import groups (3rd party, other
modules, and the current module) that kind of matches the way that our
Python code works. Where we can, this has been simplified to import
everything from the top-level indexes, which makes sorting things
alphabetically by module name much easier.
Ran js-tests.
Summary | ID |
---|---|
9310e38b67583e72be549e97daa9d580af4d5cc7 |
Description | From | Last Updated |
---|---|---|
This module is within this bundle, so it should use a relative import in a separate import group. |
chipx86 | |
Should reviewboard/common be before reviewboard/common/...? |
chipx86 | |
common should be before ui. |
chipx86 | |
reviewRequestEditorModel sorts before reviewablePageModel (R < a). |
chipx86 | |
This is in the same bundle, so it should use relative imports. |
chipx86 | |
common before ui. |
chipx86 | |
Isn't this one supposed to be a relative import since its in the same bundle? |
maubin | |
Should we import this one from reviewboard/common like we do with ReviewReply? |
maubin |
- Commits:
-
Summary ID 2eb73decd1bcf836b588ea51eefdd75efeee1308 bd39ea0be1d19e7d7acae0c4a9ca0f83e3893df6 - Diff:
-
Revision 2 (+196 -190)
Checks run (2 succeeded)
- Commits:
-
Summary ID bd39ea0be1d19e7d7acae0c4a9ca0f83e3893df6 9310e38b67583e72be549e97daa9d580af4d5cc7 - Diff:
-
Revision 3 (+198 -188)