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

[release] 4.0 tracker #204

Closed
12 of 24 tasks
yoshuawuyts opened this issue Jul 31, 2016 · 5 comments
Closed
12 of 24 tasks

[release] 4.0 tracker #204

yoshuawuyts opened this issue Jul 31, 2016 · 5 comments
Milestone

Comments

@yoshuawuyts
Copy link
Member

yoshuawuyts commented Jul 31, 2016

Major release, routing edition

Programmatic navigation is essential. But to achieve it we need to have breaking changes. And if we're going to break things, we might as well go all out again. So this issue is here to track the changes for the 4.0.0 release. All patches will be merged into the 4 branch, so that should provide an accurate representation of where things are at. Feedback and testing at any stage would be very welcome!

Changes

  • slim down server side rendering API | issue | pull-request
  • update router API to be lisp-like | issue | pull-request
  • support inline anchor links | issue
  • update router API to handle hashes by default
    • update sheet-router to handle hashes by default | issue
  • update location state to expose search parameters (query strings) | issue
  • swap state and data argument order | issue
  • move opts from app.start() to app = choo()
  • update documentation to reflect new changes
    • first pass
    • feedback round
  • update examples to reflect new changes
    • first pass
    • feedback round
  • update handbook to reflect new changes
    • first pass
    • feedback round
  • create migration guide in handbook prefixed as migration- or migrations/

See Also

@fczuardi
Copy link

fczuardi commented Sep 2, 2016

migration note:

old: send('location:setLocation', { location: path }, done);
new: send('location:set', { pathname: path }, done);

@yoshuawuyts
Copy link
Member Author

yoshuawuyts commented Sep 3, 2016

oh yeah, we've got a preliminary release branch up on choo@4.0.0-0 - missing the arg order switch, and no hash routing (yet) but that's about it (:

@pyrossh
Copy link

pyrossh commented Nov 8, 2016

If I'm starting a new project would it be better to use the 4.0.0 branch or the older one?
But need some documentation though to try it out.

@yoshuawuyts
Copy link
Member Author

Either one should work; biggest blocker right now is docs tbh - there's a
PR in, and examples are like mostly up to date so you could if you wanted
to

On Tue, Nov 8, 2016 at 2:28 PM pyros2097 notifications@github.com wrote:

If I'm starting a new project would it be better to use the 4.0.0 branch
or the older one?
But need some documentation though to try it out.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#204 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlepppEx9Wji0g3OnGSPlt8EdwPdMTks5q8AhfgaJpZM4JY7N7
.

@yoshuawuyts
Copy link
Member Author

v4 was released - closing 😁

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

3 participants