docs(configuration): update some wording of the "extends" property - #11488
Conversation
From my understanding of this documentation, there is a little bit more clarity which could be offered by different wording.
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). π Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
βΉοΈ Googlers: Go here for more info. |
There was a problem hiding this comment.
thanks @DanArthurGallagher!
|
@DanArthurGallagher interested in signing the CLA and marking this as ready for review? :) |
|
@patrickhulce I will try to get that done this evening! |
Reflect the current state, not a decision. Co-authored-by: Patrick Hulce <patrick.hulce@gmail.com>
|
CLAs look good, thanks! βΉοΈ Googlers: Go here for more info. |
|
thanks @DanArthurGallagher π |
From my understanding of this documentation, there is a little bit more clarity which could be offered by different wording.
Summary
This change tweaks the wording and the type definition around the
extendsproperty of the configuration to explain exactly which values are allowed.I feel that this could be useful since I am currently investigating some issues in a deployment of lighthouse and it was not particularly clear to me if our extension was valid or not at a glance.
Related Issues/PRs
I based this on some information I saw in #7344, including a response on that issue.
There is also the (type definition)[/types/config.d.ts]. I'm trying to find the code handling this to see if any other string does have a real value or not.