You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
app.config.ts doesn't exist in the project and adding the provideHttpClient() function to maint.ts doesn't apply. Platform browser config on the app module is overriding. Is there any reason why this project is configured so strangely? is the pro version the same or is it configured to use Angular 18 bootstrapping, injection and standalones correctly?
Otherwise, can you explain how to provide a service into the login/register component? Globally provided won't work without http functionality.
The text was updated successfully, but these errors were encountered:
The problem appears to be tha you are using a combination of legacy modules and standalone components. We can provide services to the components directly, but anything extending on or leveraging HttpClient will require the HttpClient be provided at the root for global configuration. This can't be done in the appmodule as it is ignored by standalones, and likewise, because you haven't configured the project to bootstrap app.component as a a standalone, the other configurations of appmodule are localised to the platform configuration.
I wanted to use the free version as a proof of concept in order to secure funding for the pro version. Can you confirm the pro version is configured correctly? Or otherwise upgrade the free version with instructions on how to use HttpClient?
The solution is to add the global provider for HttpClient in the appmodule along with an import for HttpClientModule, and to additionally provide each service again into the standalone component.
This is anti-pattern, but functional. Can you let me know if the pro template has the same quirk
app.config.ts doesn't exist in the project and adding the provideHttpClient() function to maint.ts doesn't apply. Platform browser config on the app module is overriding. Is there any reason why this project is configured so strangely? is the pro version the same or is it configured to use Angular 18 bootstrapping, injection and standalones correctly?
Otherwise, can you explain how to provide a service into the login/register component? Globally provided won't work without http functionality.
The text was updated successfully, but these errors were encountered: