Vue: Why is the next Vue-next not submitting code inreal time?
What problem does this feature solve?
Why is the next Vue-next not submitting code inreal time?
What does the proposed API look like?
Why is the next Vue-next not submitting code inreal time?
bailnl
All 4 comments
We don't understand your question.
LinusBorg
on 5 Nov 2018
I guess he's asking why there's no commits related to 2.X-next or 3.0
jacekkarczmarczyk
on 5 Nov 2018
Oh, thanks, that makes sense.
Because we are still prototyping.
At this stage, having everyone join in would create too much confusion.
We will share the full code alongside detailed RFCs once we feel that we reached something that is worth discussing. Then we will flesh out the details and necessary changes from the RFC feedback, and at that stage, people can start sending PRs that have a good chance of not being outdated tomorrow.
Right now, we change things a round practically in a daily basis, so people would have your a hard time following and discussing changes effectively.
LinusBorg
on 5 Nov 2018
@LinusBorg @jacekkarczmarczyk thanks
bailnl
on 5 Nov 2018
Related issues
loki0609
路
3Comments
gkiely
路
3Comments
aviggngyv
路
3Comments
paulpflug
路
3Comments
6pm
路
3Comments
Most helpful comment
Oh, thanks, that makes sense.
Because we are still prototyping.
At this stage, having everyone join in would create too much confusion.
We will share the full code alongside detailed RFCs once we feel that we reached something that is worth discussing. Then we will flesh out the details and necessary changes from the RFC feedback, and at that stage, people can start sending PRs that have a good chance of not being outdated tomorrow.
Right now, we change things a round practically in a daily basis, so people would have your a hard time following and discussing changes effectively.