ui-router can't resolve while using componentProvider
I'm working on a white label product per se that loads a data file to programmatically populate the itself, specifically in the data it loads is a component name and associated JSON data for that component while these named components are already defined in the angular module where the data is loaded into.
Using AngularJS 1.7.4 and ui-router 1.0.20 while trying to resolve ffs
in the component controller angularjs encounters an error Unknown provider: ffsProvider <- ffs
. Is this expected behaviour, is there are workaround that allows me to inject these dependencies with resolve?
I have a need to use the componentProvider because states are loaded and registered using $stateRegistry.register({...})
with each state having a component defined in a JSON file.
This is a succinct view of the design, note that it works by replacing componentProvider
with component
.
// Here's a skeleton app. Fork this plunk, or create your own from scratch.
var app = angular.module('demonstrateissue', ['ui.router']);
// Empty config block. Define your example states here.
app.config(function($stateProvider, $urlRouterProvider) {
$urlRouterProvider.otherwise('/home')
$stateProvider.state({
name: 'home',
url: '/home',
componentProvider: function() {
return 'myComponent';
},
resolve: {
ffs: function() {
return { 'msg': 'hello world' };
}
}
});
})
.component('myComponent', {
template: '<h1>foo state loaded {{ ffs.msg }}</h1>',
controller: function($scope, ffs) {
console.log(ffs)
$scope.ffs = ffs;
}
})
See the plunkr for an example
http://plnkr.co/edit/JblM9T2mTHcXvsdAovBF?p=preview
angularjs angular-ui-router
add a comment |
I'm working on a white label product per se that loads a data file to programmatically populate the itself, specifically in the data it loads is a component name and associated JSON data for that component while these named components are already defined in the angular module where the data is loaded into.
Using AngularJS 1.7.4 and ui-router 1.0.20 while trying to resolve ffs
in the component controller angularjs encounters an error Unknown provider: ffsProvider <- ffs
. Is this expected behaviour, is there are workaround that allows me to inject these dependencies with resolve?
I have a need to use the componentProvider because states are loaded and registered using $stateRegistry.register({...})
with each state having a component defined in a JSON file.
This is a succinct view of the design, note that it works by replacing componentProvider
with component
.
// Here's a skeleton app. Fork this plunk, or create your own from scratch.
var app = angular.module('demonstrateissue', ['ui.router']);
// Empty config block. Define your example states here.
app.config(function($stateProvider, $urlRouterProvider) {
$urlRouterProvider.otherwise('/home')
$stateProvider.state({
name: 'home',
url: '/home',
componentProvider: function() {
return 'myComponent';
},
resolve: {
ffs: function() {
return { 'msg': 'hello world' };
}
}
});
})
.component('myComponent', {
template: '<h1>foo state loaded {{ ffs.msg }}</h1>',
controller: function($scope, ffs) {
console.log(ffs)
$scope.ffs = ffs;
}
})
See the plunkr for an example
http://plnkr.co/edit/JblM9T2mTHcXvsdAovBF?p=preview
angularjs angular-ui-router
add a comment |
I'm working on a white label product per se that loads a data file to programmatically populate the itself, specifically in the data it loads is a component name and associated JSON data for that component while these named components are already defined in the angular module where the data is loaded into.
Using AngularJS 1.7.4 and ui-router 1.0.20 while trying to resolve ffs
in the component controller angularjs encounters an error Unknown provider: ffsProvider <- ffs
. Is this expected behaviour, is there are workaround that allows me to inject these dependencies with resolve?
I have a need to use the componentProvider because states are loaded and registered using $stateRegistry.register({...})
with each state having a component defined in a JSON file.
This is a succinct view of the design, note that it works by replacing componentProvider
with component
.
// Here's a skeleton app. Fork this plunk, or create your own from scratch.
var app = angular.module('demonstrateissue', ['ui.router']);
// Empty config block. Define your example states here.
app.config(function($stateProvider, $urlRouterProvider) {
$urlRouterProvider.otherwise('/home')
$stateProvider.state({
name: 'home',
url: '/home',
componentProvider: function() {
return 'myComponent';
},
resolve: {
ffs: function() {
return { 'msg': 'hello world' };
}
}
});
})
.component('myComponent', {
template: '<h1>foo state loaded {{ ffs.msg }}</h1>',
controller: function($scope, ffs) {
console.log(ffs)
$scope.ffs = ffs;
}
})
See the plunkr for an example
http://plnkr.co/edit/JblM9T2mTHcXvsdAovBF?p=preview
angularjs angular-ui-router
I'm working on a white label product per se that loads a data file to programmatically populate the itself, specifically in the data it loads is a component name and associated JSON data for that component while these named components are already defined in the angular module where the data is loaded into.
Using AngularJS 1.7.4 and ui-router 1.0.20 while trying to resolve ffs
in the component controller angularjs encounters an error Unknown provider: ffsProvider <- ffs
. Is this expected behaviour, is there are workaround that allows me to inject these dependencies with resolve?
I have a need to use the componentProvider because states are loaded and registered using $stateRegistry.register({...})
with each state having a component defined in a JSON file.
This is a succinct view of the design, note that it works by replacing componentProvider
with component
.
// Here's a skeleton app. Fork this plunk, or create your own from scratch.
var app = angular.module('demonstrateissue', ['ui.router']);
// Empty config block. Define your example states here.
app.config(function($stateProvider, $urlRouterProvider) {
$urlRouterProvider.otherwise('/home')
$stateProvider.state({
name: 'home',
url: '/home',
componentProvider: function() {
return 'myComponent';
},
resolve: {
ffs: function() {
return { 'msg': 'hello world' };
}
}
});
})
.component('myComponent', {
template: '<h1>foo state loaded {{ ffs.msg }}</h1>',
controller: function($scope, ffs) {
console.log(ffs)
$scope.ffs = ffs;
}
})
See the plunkr for an example
http://plnkr.co/edit/JblM9T2mTHcXvsdAovBF?p=preview
angularjs angular-ui-router
angularjs angular-ui-router
asked Nov 22 '18 at 2:28
sudosudo
188210
188210
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423069%2fui-router-cant-resolve-while-using-componentprovider%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423069%2fui-router-cant-resolve-while-using-componentprovider%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown