This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Log simple performance data from expect rule #227
Merged
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.
Write the data to a file with the same name in
~/.dts/perf/some-package-name.json
. Consumers can then read the file and display information from there. Note that tslint rules are not expected to write files, so perhaps there's a better way to log this information.types-publisher and dtslint-runner need to be updated to display the data. Here's a simple script that runs on the output of dtslint-runner:
dtslint-runner can print this out or push the json to some data store. types-publisher needs an even smaller change in test-runner to look up and print the json files for each entry in changedPackages so that it shows up in the build output.