spectator icon indicating copy to clipboard operation
spectator copied to clipboard

Cannot resolve "styleUrl"

Open timonmasberg opened this issue 1 year ago • 0 comments

Is this a regression?

No

Description

Currently, I am unable to use the newly introduced singular "styleUrl" attribute for Angular components. It seems like there was an intention of fixing this in https://github.com/ngneat/spectator/issues/631, which, sadly, for me did not resolve the issue. Furthermore, the styles component property is not working with actual styles, it will always get interpreted as a filepath...

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Component 'AuthComponent' is not resolved:
            - styleUrl: ./auth.component.css
           Did you run and wait for 'resolveComponentResources()'?
       
             at Function.get (../../../node_modules/@angular/core/fesm2022/core.mjs:29315:27)
             at getComponentDef (../../../node_modules/@angular/core/fesm2022/core.mjs:2049:12)
             at isStandalone (../../../node_modules/@angular/core/fesm2022/core.mjs:2066:17)
             at DepsTracker.computeNgModuleScope (../../../node_modules/@angular/core/fesm2022/core.mjs:6973:41)
             at DepsTracker.getNgModuleScope (../../../node_modules/@angular/core/fesm2022/core.mjs:6930:28)
             at DepsTracker.computeNgModuleScope (../../../node_modules/@angular/core/fesm2022/core.mjs:6944:44)
             at DepsTracker.getNgModuleScope (../../../node_modules/@angular/core/fesm2022/core.mjs:6930:28)
             at transitiveScopesFor (../../../node_modules/@angular/core/fesm2022/core.mjs:29143:39)
             at setScopeOnDeclaredComponents (../../../node_modules/@angular/core/fesm2022/core.mjs:29105:30)
             at flushModuleScopingQueueAsMuchAsPossible (../../../node_modules/@angular/core/fesm2022/core.mjs:28769:21)
             at _TestBedImpl.checkGlobalCompilationFinished (../../../node_modules/@angular/core/fesm2022/testing.mjs:1960:13)
             at _TestBedImpl.configureTestingModule (../../../node_modules/@angular/core/fesm2022/testing.mjs:1819:14)
             at Function.configureTestingModule (../../../node_modules/@angular/core/fesm2022/testing.mjs:1659:37)
             at ../../../node_modules/@ngneat/spectator/fesm2022/ngneat-spectator.mjs:1829:17
             at _ZoneDelegate.Object.<anonymous>._ZoneDelegate.invoke (../../../node_modules/zone.js/bundles/zone.umd.js:411:30)
             at ProxyZoneSpec.Object.<anonymous>.ProxyZoneSpec.onInvoke (../../../node_modules/zone.js/bundles/zone-testing.umd.js:300:43)
             at _ZoneDelegate.Object.<anonymous>._ZoneDelegate.invoke (../../../node_modules/zone.js/bundles/zone.umd.js:410:56)
             at Zone.Object.<anonymous>.Zone.run (../../../node_modules/zone.js/bundles/zone.umd.js:165:47)
             at Object.wrappedFunc (../../../node_modules/zone.js/bundles/zone-testing.umd.js:789:34)

Please provide the environment you discovered this bug in

Spectator v16, Angular v17

Anything else?

No response

Do you want to create a pull request?

No

timonmasberg avatar Jan 01 '24 13:01 timonmasberg