-
Notifications
You must be signed in to change notification settings - Fork 367
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
Extract Esti utils #8713
Extract Esti utils #8713
Conversation
@@ -11,10 +11,13 @@ import ( | |||
"net/url" | |||
"path/filepath" | |||
"regexp" | |||
"slices" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not crazy about files called "utils". They tend to become dumping grounds for all sorts of loosely related code. I think that all the "cleanup" code could be in a file called "esti_cleanup" or something like that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can refactor the files later, creating a lot of very small code files is also something that is objectionable
81e9b6b
to
89b65a8
Compare
49bc648
to
153e885
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Refactor Esti logic to provide more reusable functionality