-
Notifications
You must be signed in to change notification settings - Fork 216
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
Inquiry about the current status of the project #194
Comments
@aka-nse I’m also curious, it’s my go-to package any time I need to write a parser for something. Which isn’t that often but I’d quite like to know it’s around when I need it, or that new releases can be made for newer .NET 8 versions etc. Maybe a few of us users can collect a few features or issues we’d like to see addressed and put together a couple of PRs? There’s also a pre-release 3.0 version, maybe we can help the maintainers get that into shape for full release? |
Hi! Thanks for dropping by. Currently there's no activity going on, here; my own focus has moved over to https://github.com/datalust/superpower, which covers roughly the same functionality as Sprache but with error reporting improvements we need in our work. If you prefer the Sprache approach then either a fork, or a coordinated/concerted effort to update this project would be fine. A fork would probably permit moving faster/making more meaningful changes, since there's a lot of code out there relying on the intricacies of Sprache as it is today, which makes evolution awkward. HTH! |
the reason i ask is we use octostache. it uses Sprache. and now with the recent release of octostache we have a transitive CVE for System.Text.RegularExpressions GHSA-cmhx-cq75-c4mj |
Thank you for your reply and acknowledging me here 😊
…On Tue, Apr 9, 2024, 10:00 PM Nicholas Blumhardt ***@***.***> wrote:
Hi! Thanks for dropping by. Currently there's no activity going on, here;
my own focus has moved over to https://github.com/datalust/superpower,
which covers roughly the same functionality as Sprache but with error
reporting improvements we need in our work.
If you prefer the Sprache approach then either a fork, or a
coordinated/concerted effort to update this project would be fine. A fork
would probably permit moving faster/making more meaningful changes, since
there's a lot of code out there relying on the intricacies of Sprache as it
is today, which makes evolution awkward.
HTH!
—
Reply to this email directly, view it on GitHub
<#194 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYXHWK7KDMXUGOFMY4XNBTY4SMLBAVCNFSM6AAAAABCXZBSLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGMZDCMJRG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@nblumhardt Thank you for reply. Then, could you please append announce and guide to superpower on README? |
This is the same issue as #149 and on that issue I mention how we solved this in my library. |
Hello.
I like this parser combinator library because it is easy to use, but I noticed that there haven't been any recent updates or commits.
I was wondering if the project is still being actively developed and maintained.
Can I use or contribute this project still?
Or should I fork into new project?
Thank you for your time.
The text was updated successfully, but these errors were encountered: