Skip to content
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

Split huge files into smaller units #476

Closed
japgolly opened this issue Aug 12, 2021 · 12 comments · Fixed by #586
Closed

Split huge files into smaller units #476

japgolly opened this issue Aug 12, 2021 · 12 comments · Fixed by #586
Assignees
Milestone

Comments

@japgolly
Copy link
Contributor

Atm we have huge files like lib.scala with tons of stuff in them. It would be nice to split this into a more traditional structure.

@armanbilge
Copy link
Member

@japgolly Do you still want to do this?

@japgolly
Copy link
Contributor Author

japgolly commented Sep 4, 2021

@armanbilge Oh no way lol. I absolutely do not want to do this but I was resolved to because it'll be valuable and make future maintenance easier. If you want to do though, feel free! I would be overjoyed lol

@armanbilge armanbilge removed this from the v2.0.0 milestone Sep 4, 2021
@armanbilge
Copy link
Member

armanbilge commented Sep 4, 2021

Lol! @sjrd also strongly recommended against in #545 (comment). I (begrudgingly) think we should consider closing.

@japgolly
Copy link
Contributor Author

japgolly commented Sep 5, 2021

My understanding of that comment is that he was against doing both changes at the same time. git blame isn't a compelling reason to me anyway for not improving the codebase. We should do the best we can by git but the value of the codebase far outweights the value of git, especially on a project like this where it's 99% facades. Plus do keep in mind that git blame is already useless due to reformatting. If we really want to know the history, git blame isn't the best way and it can still be achieved via git.

@armanbilge
Copy link
Member

Ah, makes sense now. Ok, well I'll mark this help-wanted since basically anyone can do it.

@sjrd
Copy link
Member

sjrd commented Sep 5, 2021

My understanding of that comment is that he was against doing both changes at the same time.

That's indeed what I was saying.

@japgolly japgolly added this to the v2.0.0 milestone Sep 6, 2021
@japgolly japgolly self-assigned this Sep 8, 2021
@japgolly
Copy link
Contributor Author

japgolly commented Sep 8, 2021

Automation coming to save the day................. 👀

@japgolly
Copy link
Contributor Author

japgolly commented Sep 9, 2021

Hey @armanbilge just a an FYI, this is like 85% done but something came up, I got interrupted and it looks like I wont online for 4 days or so. Not even for reviewing your PRs unfortunately. Do with that info whatever you think is best, I'll be back next week, and sorry for any inconvenience :)

@armanbilge
Copy link
Member

No worries, have a nice long weekend I hope!

@japgolly
Copy link
Contributor Author

looks like I wont online for 4 days or so

Ah yeah, sorry but I've had a bit of a medical emergency that blew out way beyond 4 days. It's going to take quite a while to resolve but slowly, slowly I'll starting coming back bit by bit. Sorry about the inconvenience and feel free to maintain away without my involvement. Don't want to hold anyone back.

@armanbilge
Copy link
Member

Don't worry at all, wishing a healthy recovery so please take all the time you need. Thanks for clearing the PR queue, I'll keep chugging away.

@japgolly
Copy link
Contributor Author

Thanks @armanbilge !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants