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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
[email protected]
Patch Changes
#7
5caf325
Thanks @zaripych! - fix: prevent pnpm from asking questions when install command is run#6
b7ba5a3
Thanks @zaripych! - feat: this one introduces a feature which allows refactor-bot to perform aggregation and other more advanced analytics in the codebaseWe ask the model to generate a script for us that can use
ts-morph
directly and execute map/reduce in the repository. The script is ran in a separate process for a bit of safety and can also be moved to a Docker container.#8
438ef72
Thanks @zaripych! - refactor: the caching layer of the refactor bot now supports eventsThe events make it easier for separation of concerns between modules.
For example, it now allows us to collect refactor results from multiple layers of code without having to pass around mutable references.
This also allows us to measure the performance of the refactor bot and calculate the costs associated with OpenAI api.
All of this to prepare for the refactor bot to have automatically evaluate itself and setup benchmarks that could be used to further measure and improve it's performance.
#2
2d7df8e
Thanks @zaripych! - fix: sanitised result of the functions to exclude user's repository path from the output of the functions#2
b04ab6b
Thanks @zaripych! - fix: introduced a parameter which allows us to control how TypeScript projects are loaded in monorepo scenariosIe if
useCombinedTsMorphProject
istrue
then the original strategy is used - where we load all TypeScript projects into a single ts-morphProject
. This allows cross-project references to be easily found and traced. The disadvantage of this approach is that it might not just work if projects settings are different.#7
5caf325
Thanks @zaripych! - fix: format function would leave one variable unformatted when it is preceeded with an empty string#7
5caf325
Thanks @zaripych! - fix: the references function would return empty array when includeFilePaths parameter is used for a node built-in#3
401d3b5
Thanks @zaripych! - fix: the package manager not being determined correctly if "packageManager" field is specified in the package.json#4
ef77b8d
Thanks @zaripych! - fix: formatting going to infinite cycle if the values contain placeholders#2
b65fe19
Thanks @zaripych! - fix: module imports function is now smarter and doesn't include results from in-repo modules that import themselvesThis should ensure that when we _ are looking for imports of "package" where the "package" _ is one of the monorepo packages - we do not include itself importing its own internal files.
#2
b04ab6b
Thanks @zaripych! - fix: added new GPT4 models to the list of possible choices