GoogleChromeLabs / GoogleChromeLabs/extension-update-testing-tool
Displaying the Extension ID
- Dominant language
- JavaScript
- Stars
- 288
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
I've been having issues with mixed `.pem` keys and not knowing which PEM keys relate to which extension ID so I've been using this repo as a way to validate the ID in the policy e.g. `KEY_PATH=./my_other_pem_key.pem WRITE_KEY=1 npm start` (`KEY_PATH` is a variable I added not currently in this repo) which made me think it would be great to have the extension ID somewhere displayed before downloading the policy.
This could be a problem only I'm having but as far as I can tell I can't see a clear way in CWS to validate which PEM key relates to which extension ID?
See example below.
Contributor guide
Research direction
Start by running the repository with npm start and follow the flow that displays or downloads the policy. Identify where the extension information is presented, then add the extension ID before the policy download and verify that it is visible for the PEM-key example described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100