Feat: add logger and performance measurement #151
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.
Reimplements #138 but for the monorepo setup.
Changes:
LogOutputChannelnamedPretty TypeScript Errorsmeasuremethod for the logger to measure the execution time of certain code pathsuriStoretoMapinstead of aRecord.I haven't added the
logger.measurecalls, because I think we should keep that just for development purposes for now. I'm planning on creating an issue template where we can guide the user to add the cpuprofile and our extension log file. But I need to research how that works first. We can add the measurement statements when that is complete.