dependabot-preview[bot] on npm_and_yarn
dependabot-preview[bot] on master
build(deps): [security] bump ss… Merge pull request #327 from ui… (compare)
dependabot-preview[bot] on npm_and_yarn
build(deps): [security] bump ss… (compare)
dependabot-preview[bot] on npm_and_yarn
dependabot-preview[bot] on master
build(deps-dev): bump @babel/co… Merge pull request #326 from ui… (compare)
dependabot-preview[bot] on npm_and_yarn
"dependencies": {
"@angular/animations": "^8.2.9",
"@angular/cdk": "^8.2.3",
"@angular/common": "^8.2.9",
"@angular/compiler": "^8.2.9",
"@angular/compiler-cli": "^8.2.9",
"@angular/core": "^8.2.9",
"@angular/forms": "^8.2.9",
"@angular/material": "^8.2.3",
"@angular/platform-browser": "^8.2.9",
"@angular/platform-browser-dynamic": "^8.2.9",
"@angular/platform-server": "^8.2.9",
"@angular/router": "8.2.9",
"@angular/upgrade": "^8.2.9",
"@uirouter/angular": "6.0.1",
"@uirouter/angular-hybrid": "9.0.0",
"@uirouter/core": "6.0.1",
"@uirouter/rx": "^0.6.5",
"core-js": "^2.5.4",
"zone.js": "^0.10.2",
"rxjs": "^6.5.5",
"rxjs-compat": "^6.5.5",
}
@Gabe So all my state configurations look something like this:
config.$inject = ['$stateProvider', '$provide'];
function config($stateProvider, $provide) {
$stateProvider
.state('engagements', {
url: '/engagements',
redirectTo: 'engagements.home',
template: '<engagement-app />'
})
.state('engagements.home', {
url: '/home',
views: {
'main@engagements': {
template: '<parent-engagement-list />'
}
}
})
If that helps clarify things.
@uirouter/angular-hybrid
brings 1.x along for the ride, but it's best to do the 1.x upgrade while still your project is still pure angularjs
I'm wondering why the StateRegistry.get() method doesn't allow for a more specific/constrained search. I have a situation where our application is trying to decide whether or not a state has already been registered, but it's getting a match on a parent future state declaration - which, is kind of throwing a wrench in our logic. There doesn't appear to be a way to ask the StateRegistry if a specific state is present or not, without accidentally matching this future state.
Maybe I'm not so much wondering "why" the .get() method matches 'example.**' when trying to fetch 'example.specific-child' - I mean, it makes sense; the wildcard state would match at runtime. It's just inconvenient for my needs, since I need to make sure that 'example.specific-child' actually exists or not during configuration and there doesn't seem to be a way to query the StateRegistry in this manner.
exactMatch
or ignoreWildcards
param added to the method signature would be ideal)