Closed gshackles closed 7 years ago
+1
Seems like nothing is being merged in this library. PR https://github.com/HubSpot/humanize/pull/92
Looks like that should take care of this, thanks! π Any ETA for that making it out into a release?
@gshackles The definitions is already published to@types/humanize-plus
, you can start using it right now π !
Feel free to send PR's to DT and I can π the changes.
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/16977
Ah awesome. That said, in #92 you added the type definitions directly into this repository, so even better would be to push an updated package out that includes that definition and avoid the need for pulling in the separate definition from DT π
You are correct, however no one merges anything in this library, unless you have admin privileges to merge?
I opened that PR March 3rd
Doh, sorry, that's what I get for reading too quickly...I saw the closed PR but missed the fact that it wasn't actually merged. In that case, I suppose the typing will do the trick for now!
π Yea... if you can convince the maintainers of this library to merge or accept a Typescript definition, we can make another PR.
Hey, someone with admin privileges hereβ
Internally we merged this with our larger i18n library so it's a bit of a split for us to maintain both. You're more than welcome to fork and maintain & I'm happy to work with whoever wants to get things pointed there.
Also, thanks for taking a look at this and being proactive to supply the solution independent of lack of response.
Whoops missed this til now. Thanks for the response, @FranDias!
If this isn't really being updated anymore then I think just leaving the separate type package seems reasonable. We don't have a real need to fork/maintain at this point, but if the need arises we can revisit.
Closing this issue out then, thanks all!
I've started working with humanize as part of a TypeScript application, and ended up just going ahead and creating definitions for all the exposed methods. Is this something you'd be willing to include directly in the repository and npm package? If so I'm happy to submit a PR with the changes. If not I can create and maintain a separate typings repository to host the definitions, but it's a much better user experience to have it directly in the package.
Let me know! π