1.0 beta checklist

[christopherthielen]

List of 1.0 BC: #2219

Blockers

Merge

• fix($urlRouter): resolve clashing of routes #1585 Sort url rules by specificity (Add to BC list)
• 48aeaff (maybe) Investigate if we should keep the "avoid-url-resync-after-transition" code
• f9b43d6 (maybe) Figure out if/where $viewContentLoading goes in new architecture
• 02e9866 path parameter slash encoding/decoding
• 77fa11b squash trailing slash for optional params
• 20d6e24 proper default value for array query param
• 3831af1 ui-state directive
• a9ff6fe ng-class syntax for ui-sref-active
• 9dc31c5
• e401024 Allow params: { foo: { type: "int" } }
• 6a371f9 Fix param type configuration rule
• b5130bb recognize squashed url properly
• d31b333 dots in url
• 9dc31c5 ui-sref fix
• 7c91403 ui-sref fix
• c219e80 $sniffer pushstate detection
• 9b6d9a2 animate ng1.4 compat
• 1be1379 animate fix
• 3d7f267 ui-sref-active + eq on same el
• c4fec8c prototypal inherit state.data
• a1f0755 options for $stateChange* events
• 71d7469 add params to isState filter
• 4b7f304 allow spaces in url params
• Merge in anything else committed to https://github.com/angular-ui/ui-router/commits/master/src/stateDirectives.js
• Find remaining commits from 0.2.11 through 0.2.16 that should be merged to 1.0

Bugs

https://github.com/angular-ui/ui-router/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A1.0

Features

• Retain resolved data during transition redirect
• Consolidate StateParams and ParamValues classes
• Baked in redirectTo processing, as an onStart hook Child default state issues with the ui-sref & URL #948
• Add/remove states during runtime (stateRegistry.ts)
• Earlier exit hook than onExit... maybe integrate with onBefore afcfe95
  • should fire before an onStart hook that redirects if a user is not authenticated, for example);
  • Better integration with view code (controller/component).
• Make path parameters non-optional by default (add to BC)

Chores

branches, repositories, orgs

• Create separate repo for ui-router-core
• Branch angular-ui/ui-router master to 0.2.x
• Merge (or move?) feature-1.0 to master
• Move core code to ui-router-core
• Release first version of ui-router-core
• Import ui-router-core into angular-ui-router
• Release angular-ui-router beta
• Release ui-router-ng2 alpha
• Find a home for ui-router StateVis and TransitionVis
• Find a home for new demo app

common.ts

• Remove unused code from common

TS and ES6

• Ensure tslint passes rules
• Configure build with tslint
• ES6ify remaining ES5 classes

Non-Blockers

(but will block a release candidate)

Docs

• docs -- update for http://typedoc.io docs generation
• recipes and approaches
• interactive architecture overview (statevis/transitionvis)
• Add lots of docs and comments to the new demo app

[nateabele]

@wesleycho @christopherthielen What would some alternatives to ng-docs be?

[christopherthielen]

I do not know, but there's gotta be something out there that does something cool with typescript

[nateabele]

This looks pretty.

[royaldark]

@christopherthielen Will the ui-state directive be available in an upcoming 0.2.x release, or only in 1.0?

[nateabele]

@royaldark Both.

[areologist]

@nateabele Can I be of any assistance with respect to the ui-state merge or other 1.0 items?

[christopherthielen]

Yes feel free to do the ui-state merge!

[areologist]

Thanks, Chris. I just started a new job but I'll start on this soon.

[eeelated]

@christopherthielen Does the 1.0 version already support parallel state? I have a project that has a great need of parallel state. And how close is 1.0? I'm not familiar with things enough to understand what the checklist items are:). I can help with testing 1.0 against an existing application though, and would also love to help with any simple tasks from the checklist.

[nateabele]

Does the 1.0 version already support parallel state?

Not yet unfortunately.

And how close is 1.0?

Very close. Helping with the issues on this list will make it closer. Testing against existing apps is also important.

[atian25]

any time plan for 1.x publish ?

[christopherthielen]

I'd like to get beta out this week. there are going to be a few breaking changes between alpha and beta. We'll let it bake for a few weeks. if all goes well, then I think we're ready for a final release.