-
Notifications
You must be signed in to change notification settings - Fork 137
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
v1.0 roadmap? #112
Comments
|
I'll also add that we need to fix code styling and perhaps take another look at eslint rules that are currently applied (biggest one on my mind is ";") :) |
I was referring to these types of issues:
One of the first code snippets from docs does not produce expected output! |
Thanks @gt3, checking. |
🤔 |
Technically the rendezvous should work as described in the docs. I believe this is a drawback of using callbacks. We might need something lazier? I checked 0.5 with the same results. @ubolonton ? |
I've been following this project for past few months now. I'm sure there are others like me in the community who would also like to see this project gain momentum and finally achieve production-ready status.
Let's start by making a list of tasks on the critical path to <<1.0>> so we can better focus our resources on shipping out a stable product first. I'd like to ask primary contributors - @ubolonton and @hung-phan to guide us in defining the necessary scope of work.
New feature development that includes, API extensions and new language features, should be stalled/deferred until we have addressed all edge cases and shortcomings preventing this project from reaching the CSP standard.
I am pretty new around here but I know that if there is one project that deserves more attention in the Javascript ecosystem, it is this one and I'm excited to learn. So how can I help?
Happy New Year! :)
The text was updated successfully, but these errors were encountered: