| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I'm concerned that allowMultiple will be used to bypass the configuration requirements rather than enforce them. |
Sorry, something went wrong.
There was a problem hiding this comment.
OK, looking more closely: I understand the reasoning for wanting to add allowMultiple but I think the downside is much greater than the upside. The benchmark tests are not exhaustive. They are minimal and that is definitely on purpose. (Otherwise, they would take forever to run.) I think it would be best to make these conform to the existing tests and not add allowMultiple which will probably end up being abused at a later date.
Sorry, something went wrong.
|
Hmm, I thought about it being abused but assumed that such tests don't get changed often, therefore, they can be validated more thoroughly to avoid such abuse. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
There was a problem hiding this comment.
Code LGTM but I am not a fan of adding these tests in general. But I am not going to block this either.
Sorry, something went wrong.
|
@BridgeAR is there a special place for these? I just put them where other such tests were. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Rebased so fix jinja LICENSE thing in CI. CI: https://ci.nodejs.org/job/node-test-pull-request/16554/ |
Sorry, something went wrong.
|
Resume build: https://ci.nodejs.org/job/node-test-pull-request/16574/ |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist