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

General Question about the future of Folktale #228

Open
marcog83 opened this issue Oct 26, 2020 · 5 comments
Open

General Question about the future of Folktale #228

marcog83 opened this issue Oct 26, 2020 · 5 comments

Comments

@marcog83
Copy link

First i'd like to thank you for this AMAZING piece of code. I love folktale.

I read in a comment that finding time to mantain the library is difficult.
#226 (comment)

We would like to use folktale inside our Internal Project. Mostly for building Validation of data.
I'd like to know if you plan to keep working on it, or how do you envision the future of this library?
Thanks a lot

@robotlolita
Copy link
Member

I still don't have much bandwidth to maintain it, and since I'm not using JavaScript anymore it's hard for me to justify most development effort. I'm still answering questions and fixing bugs, but larger projects like supporting TypeScript are not on my radar for now. Although if anyone wants to take in development maintainership for this project I would be happy to support.

@opiation
Copy link

@robotlolita, I would love to help with maintaining this project. Would you be open to discussing this over audio/video call to see if/how I can help and what that help would look like?

For context, I actively work in Typescript and Javascript every day and would be quite comfortable with the efforts needed to embrace Typescript for this library, ES modules and the like. I've been writing my own similar library natively in Typescript to have a slightly more JS/object-friendly adaptation of fp-ts but felt that my efforts might be better spent supporting existing libraries rather than creating yet another JS/TS lib.

@robotlolita
Copy link
Member

@opiation sorry, I missed the notification for this.

Since there isn't much happening in the repo now, any help would be welcome, really. I'm honestly not really sure what most users of the library are interested in seeing. When I was working on JS projects, the one thing I missed the most was TypeScript support. I ended up just writing the typings and never got around refactoring the project to be a TypeScript-first one---there is a significant amount of things that currently relies on reflection.

I'd say the thing missing right now is deciding where to push the library towards (e.g.: proposing a roadmap). The existing roadmap is probably not that relevant anymore, 'sides the TypeScript part.

I'm not huge on calls, but feel free to either DM me on Twitter (https://twitter.com/robotlolita), or email me directly at queen at robotlolita. me

@tomholford
Copy link

@robotlolita Any idea how close the Typescript PR #157 is to completion? That could breathe new life into this project

@robotlolita
Copy link
Member

@tomholford no one's working on it currently. But it's missing types for the adt part basically. it should be possible to encode that in typescript these days, though i'm not sure if it would require changes to the API as well.

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

No branches or pull requests

4 participants