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

Misc Internal Improvements #17210

Open
3 of 16 tasks
ephys opened this issue Mar 26, 2024 · 5 comments
Open
3 of 16 tasks

Misc Internal Improvements #17210

ephys opened this issue Mar 26, 2024 · 5 comments
Assignees
Labels

Comments

@ephys
Copy link
Member

ephys commented Mar 26, 2024

I'm trying out task lists as a way to keep track of a bunch of small improvements we can implement, as it doesn't make much sense to create an entire feature request for changes this small.

Current Progress

  1. dependency type: refactor
    WikiRik
@ephys ephys added the meta label Mar 26, 2024
@ephys ephys self-assigned this Mar 26, 2024
@github-actions github-actions bot added the pending-approval Bug reports that have not been verified yet, or feature requests that have not been accepted yet label Mar 26, 2024
@ephys ephys removed the pending-approval Bug reports that have not been verified yet, or feature requests that have not been accepted yet label Mar 26, 2024
@WikiRik
Copy link
Member

WikiRik commented Mar 26, 2024

Fork pg-hstore and move toposort to monorepo because of the size of the files? Or is there another reason why you want to handle them differently?

@ephys
Copy link
Member Author

ephys commented Mar 26, 2024

Ahah, I thought my phrasing was not fully clear. I didn't use fork for toposort because we already forked it, but they're both very small packages that fit well with the monorepo so what I mean is move them both inside of the monorepo

@WikiRik
Copy link
Member

WikiRik commented Mar 29, 2024

Similar to hstore and toposort, do we want to archive the sequelize-pool repo and move it to the monorepo as @sequelize/pool? We should check with Sushant as well since they still respond to issues there

@ephys
Copy link
Member Author

ephys commented Mar 29, 2024

Definitely need to check first, but that would be nice as well

@WikiRik
Copy link
Member

WikiRik commented Mar 29, 2024

See sequelize/sequelize-pool#54

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

No branches or pull requests

2 participants