feat: initial snyk-fix package setup & loadPlugin functionality #1659
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lili2311
force-pushed
the
feat/initial-snyk-fix-setup
branch
from
07be92b
to
f9ba3b3
Compare
lili2311
force-pushed
the
feat/initial-snyk-fix-setup
branch
5 times, most recently
from
4e60b73
to
806289f
Compare
JackuB
approved these changes
Mar 4, 2021
- setup a new snyk-fix workspace for fix package functionality - basic loadPlugin functionality & types added - a couple of basic tests to ensure loadPlugin is working as expected
lili2311
force-pushed
the
feat/initial-snyk-fix-setup
branch
from
806289f
to
a6b708e
Compare
This was referenced Apr 27, 2023
This was referenced Jun 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Where should the reviewer start?
Check the package.json & any relevant release setup mostly 馃檹 all the code will change a lot after this initial version and is there mostly to have basic skeleton + tests
How should this be manually tested?
npm run testinside the packageAny background context you want to provide?
Package tests will not trigger until this functionality is added shortly.