feat: Speed Up Enthistory Codegen With Concurrency #49
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.
Description
Small bit of optimization on codegen speed, turns out the slowest part of the enthistory codegen is actually the imports correction in the print func. A very recent issue was opened in the go repo explaining this exact issue with the imports formatting - especially in regard to ent.
golang/go#66802
Motivation and Context
enthistory & ent codegen seemed to slow down after the rewrite
How Has This Been Tested?
Done some general testing, seeing anywhere from 10%-30% improvements depending on the size of the project
Otherwise this is a non functional changeset with no outcomes on downstream users
Types of changes
Checklist: