Change ReviewRequest.createFromCommit to return a promise.
Review Request #11632 — Created May 27, 2021 and submitted
This change updates the post-commit review request creation method to
return a promise instead of using callbacks for success and error.
- Ran js-tests.
- Created a post-commit review request.
Summary | ID |
---|---|
d63d650176739c578c24bf16243b4c1eadb186d2 |
Description | From | Last Updated |
---|---|---|
Col: 44 'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6'). |
reviewbot | |
Col: 27 'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6'). |
reviewbot | |
Col: 44 'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6'). |
reviewbot | |
The description went missing. |
chipx86 |
-
The code itself looks fine.
Before I jump into the other files, the thing we just really need to figure out is what we consider to be API-stable. While I have no idea which parts of the JS codebase are in use elsewhere, we do offer JavaScript extensions and those are in use extensively at some places. So I'm tempted to say we should avoid breaking function signatures wherever possible, especially in areas that interface with the API (like
resources/
).The updates here remove
options
and replace it with acommitID
argument. I'm fine with this, but if we do it, we should retain backwards-compatibility (check whether we have an object or a string) and go through a deprecation warning process like we do on the Python side.
- Commits:
-
Summary ID 720e11e60f4948a00e6f6e93bb5c205fbccc1764 efa54a820be84bc5c59484b3186ce53e298cb8a7