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

chai-subset is unmaitained #1616

Open
GustavoOS opened this issue May 13, 2024 · 8 comments · May be fixed by #1621
Open

chai-subset is unmaitained #1616

GustavoOS opened this issue May 13, 2024 · 8 comments · May be fixed by #1621

Comments

@GustavoOS
Copy link

Hi

As in debitoor/chai-subset#84 , chai-subset is unmaitained. The biggest contributor no longer has owner rights, but proposed to fork and maintain it. Is chaijs interest in owning the fork?

@keithamus
Copy link
Member

Sure. Happy to add it to the org.

@43081j
Copy link
Contributor

43081j commented May 13, 2024

it may also be worth just building this functionality into chai itself, as some variant of includes

much of the logic in chai-subset exists in chai already, just not for this particular usage (e.g. recursively checking equality of nested types)

maybe this could just be achieved by some modifier of includes ("partial" or something, or includes.subset)

just a thought

@keithamus
Copy link
Member

I am happy to do that, but we should only do that after transferring or at least discussing with the owners/maintainers.

@eagleeye
Copy link

Hey guys, I'm the main contributor to the chai-subset while I was working in Debitoor. I couldn't convince them to transfer ownership. I think it should be fine to add it into core functionality of chai of fork the repo and support the fork. The question is what is preferrable for the chaijs org?

@keithamus
Copy link
Member

I think it would be great to clarify our intent to debitoor before moving forward. There's a strong chance if we fork the library into this org, or otherwise integrate changes into core, then the debitoor library will be rendered obsolete. I don't want that to come as a surprise to them. So I think a good next step is perhaps contacting them again, if you don't mind?

In terms of next steps beyond that, I think we can look at what it'll take to integrate directly into core (PRs welcome 😉) but also I think having a fork (or ideally the source repo) under the chaijs org for archival purposes would be a good step also.

@zetxek
Copy link

zetxek commented May 15, 2024

Thanks for the convo and for letting us know! Both here and in debitoor/chai-subset#84 :). 👋 Adrián from SumUp (formerly Debitoor) here.

While debitoor as an org is not active, it's now part of @sumup :) - and while we do maintain some open source software (https://github.com/sumup-oss), as you have seen, chai-subset (https://github.com/debitoor/chai-subset/issues) is not among the well-kept ones.

Feel free to fork and integrate the codebase into chaijs :)

For the ownership transfer I'd have to look into the process to transfer it (might take longer). With the matter of the original repo going obsolete - maybe we could add a notice to the readme and mark it as deprecated? (given that the last commit is from 2017, 7 years ago)

@eagleeye
Copy link

Cool, I'll prepare a PR to chai in the nearest future. I believe that chai-subset is a good fit for core functionality of chai.

@koddsson koddsson linked a pull request May 20, 2024 that will close this issue
@koddsson
Copy link
Member

I hope you don't mind that I hacked on this quickly while waiting at a airport. I tried to make sure that the history was preserved in doing this.

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

Successfully merging a pull request may close this issue.

6 participants