vizipi[bot]
commented
1 year ago Pull request analysis by VIZIPI
Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below ) Feedback always welcome
Reviewers with knowledge related to these changes
| Match % | Person | Commit Count | Common Files |
|---|---|---|---|
| 100.00 % | AbigailDeng | 14 | 4 |
Potential missing files from this Pull request
files commonly committed with a subset of this pr, but not committed this time. (click to collapse)
| File | Percentile | rate |
| package.json | 50.00 % | 1 out of 2 times |
| yarn.lock | 50.00 % | 1 out of 2 times |
| dist/aelf.umd.js | 50.00 % | 1 out of 2 times |
| dist/aelf.umd.js.map | 50.00 % | 1 out of 2 times |
| dist/aelf.cjs.js.map | 50.00 % | 1 out of 2 times |
| dist/aelf.cjs.js | 50.00 % | 1 out of 2 times |
| .github/workflows/main.yml | 50.00 % | 1 out of 2 times |
| jest.browser.config.js | 50.00 % | 1 out of 2 times |
| test/unit/chain/chainMethod.test.js | 50.00 % | 1 out of 2 times |
| jest.node.config.js | 50.00 % | 1 out of 2 times |
Committed file ranks
(click to expand)
80.71%[test/unit/util/token.proto.json] 92.52%[test/unit/util/transform.test.js] 92.52%[README.md] 66.93%[src/util/transform.js]
Parsing can be problematic when the contract result contains an array of enumerated types