-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap #35
Comments
Please ensure Stage 2 is opt-in for the module author. Also, a |
That kind of destroys the point... |
If it is not opt-in it will generate too much noise.
These are a few reasons why making any automated checks opt-in. |
The frequency at which a module is updated should be considered as well? |
For the Gitlab / Bitbucket integration, what needs to be done to move those forward? |
Stage 0
Stage 1
deno info --json
on ts/js files in the repository to get a dependency graph. Store in$NAME/versions/$VERSION/meta/deps.json
. This tree should be a multi entry point graph with nodes and edges, not a simple tree. (feat: dependency analysis #62)deno info --json
work with more modules (eg modules using decorators)Stage 2
deno fmt
on all files in repo and store list of failed files in$NAME/versions/$VERSION/meta/analysis.json
deno lint --json
on all files in repo and store list of failed files + the diagnostics in$NAME/versions/$VERSION/meta/analysis.json
deno check
on all files in repo and store list of failed files in$NAME/versions/$VERSION/meta/analysis.json
LICENCE
&README.md
file there, are dependencies pinned to specific version) and store this in$NAME/versions/$VERSION/meta/analysis.json
.Future
deno doc --json
on all files in the repo and store the output in$NAME/versions/$VERSION/docs/$FILEPATH.json
$NAME/versions/$VERSION/stripped/$FILEPATH.json
The text was updated successfully, but these errors were encountered: