-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Error encountered resolving symbol values statically when calling 'createFeatureSelector' #611
Comments
Your https://github.com/duartealexf/web-labs/blob/master/src/app/state/reducers.ts#L21-L24 |
Okay I fixed it like you said and now everything works! Thanks! However... i get this error after building successfully: A very similar message is also shown in the example-app for me, but there it does compile and does not indicate an error. If I hover the red underline the same message is shown: Is there a way to fix this? Thank you again. |
Hi @brandonroberts, I've seen a lot of issues in StackOverflow and in this repo about this When I build my project (I sent you before) using Now I built the platform/example-app from this repo and VSCode complains about type incompatibility as well. But when I build it using This is platform/example-app: and the message is:
While the red underline in line 49 has this message:
Can you help me understand what is going on here? How do we get rid of these messages? How to build without the compiler complaining about this type mismatch? |
I'm submitting a...
What is the current behavior?
Running into "Error encountered resolving symbol values statically" error when calling function "createFeatureSelector", when building with:
ng serve --host 0.0.0.0 --disable-host-check --vendor-chunk --extract-css true --aot
.Without the --aot flag it builds fine.
Expected behavior:
It should build using the --aot flag.
Minimal reproduction of the problem with instructions:
docker-compose build
thendocker-compose up
(which will run the 'ng build' command mentioned, with --aot).Version of affected browser(s),operating system(s), npm, node and ngrx:
node v8.7.0
npm v5.4.2
yarn v1.2.0
ngrx 4.1.1
browser: N/A
OS: macOS High Sierra 10.13.1
Other information:
Here's a print of the situation:

I really don't know why this error suddenly started happening. I tried to redeclare a copy of the function locally, but since i need to import the createFeatureSelector to do so, i went back to square one. I really need to know if this is at least happening to other people or if my mac is trying to drive me nuts!
Thanks everyone.
The text was updated successfully, but these errors were encountered: