-
Notifications
You must be signed in to change notification settings - Fork 3k
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
V1.1.0 - TypeError: Cannot read properties of undefined (reading 'inherit') #3851
Comments
Make sure that you manually specify @uirouter/core in your package.json |
Hello, thanx for the answer. I did it, i added "@uirouter/core": "^6.1.0" dep into package.json but still have the same error. Do i need to inject it into the angularjs scope? |
Are you using any other packages from uirouter? |
Ah sorry, didn't catch! No, no other package, only angularjs and core. |
Which version did you update from? |
1.0.30 and it works perfectly! |
I can't see anything that'd make it break. Can you try uirouter/core 6.0.8? |
Just tested using core 6.0.8 and that fixed the problem, works like a charm! |
6.0.9 breaks as for 6.1.0 |
I think I found out what the problem is. Do you have params declarations as strings instead of objects? |
Uhmmm, params in state are always declared as objects like this:
I've looked into all the project and unfortunately i didn't find any param defined as string, only objects. |
You just showed me the issue :D. The value of the param is null which is not an object :D |
Ok, i'm going to cleanup my code! Thank you!!!! |
Well, I think your case is still supported so I'll add a fix for your case! |
@p3pp8 I'm having some issues reproducing the issue in the unit tests. Would you be able to send me a basic state declaration structure that makes this fail? So that I can test my fix. |
Hello @wawyed, the example in the post above is extracted from my project (with some renaming) and is a basic state declaration with default params set to null. I think they should've been declared like this:
Thank you for the support! |
If you change it as above the error disappears? |
We have unit tests that test such functionality but they pass |
I'm going to try! |
Nothing to do, i've changed all params to have { value: null } instead of null but the error is still there... |
Okay... so it's not that.. would you be able to put a breakpoint where it errors and see which param is trying to access? |
The project is very complex and loads many angular components with states, i'll try to do my best but it's not as simple as put a breakpoint |
The loop in stateParams.js kept adding the word 'chunk' in parentParamsKeys. I don't know what causes that, but I changed the loop from
to
now it works. |
I think i have to wait for a new release, but that's not a problem. Thank you guys! |
@christ182 can you inspect parentParamsKeys, check Object.keys(parentParamsKeys) wondering if for some reason there's some enumerable properties added to that array? |
@wawyed Object.keys is working as expected. It's the loop that does not behave properly. |
I found the reason for mine.
Although, I have this Array.prototype.chunk code in for some time now. I don't understand how it suddenly broke. |
The reason I said Object.keys() it's because it retrieves the enumerable properties of the array. I wasn't referring to the existing Object.keys. Regardless I think I have a fix based on your latest comment. |
I do suggest though that you use Object.defineProperty() instead and make chunk non enumerable to avoid further issues. |
@wawyed Can V1.1.0 be released as soon as possible? |
@ckLocal is this not what you need? https://www.npmjs.com/package/@uirouter/angularjs/v/1.1.0 |
@wawyed Yeah, this is what I want, that's great. |
Hi, I'm running into this same error and I don't see a similarity to @p3pp8's configuration. Here's where my states are defined. Is there an incompatibility here? I'm upgrading from angular-ui-router 0.4.2 to @uirouter/angularjs 1.1.0 (yes, this is a legacy app that I must support)
|
Indeed that Here's what the loop should look like. Someone forgot to add the hasOwnProperty() check, to omit prototype properties and functions.
|
@EoinGriffin-AI You shouldn't make custom methods into prototype enumerable. Can you show me the code that adds those methods? |
Ah you're right, thanks for pointing out that they're non-standard functions. It's some old custom code added many years ago to our codebase. I can change their definitions to not be enumerable. |
After updating to version 1.1.0 i'm not able to run my app anymore. I use AngularJS 1.8.3.
I did not find any changelog and/or migration instructions. Any help is really appreciated.
The text was updated successfully, but these errors were encountered: