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
This line is causing a lot of console output and warnings when using the StarterKit.
I agree that it seems unexpected but should we give a warning? Or maybe it should be something that can be enabled/disabled?
In the NextJs SDK there are no warnings (and no strong types).
In the StarterKit there are several components that can use either a page/route field or a specific data source aka component field. That has been solved by using multiple fields and hereby the warning is triggered.
I would at least suggest that the out-of-the box configuration should not give a lot of warnings.
It might also be that it would be meaningfull with a binding that solves this fallback scenario (use component field if a data source value but fallback to route field) instead of building the logic in the head application over and over.
The text was updated successfully, but these errors were encountered:
This line is causing a lot of console output and warnings when using the StarterKit.
I agree that it seems unexpected but should we give a warning? Or maybe it should be something that can be enabled/disabled?
https://github.com/Sitecore/ASP.NET-Core-SDK/blob/44c614011a9344e36624272b3f067017903eae3e/src/Sitecore.AspNetCore.SDK.RenderingEngine/Binding/SitecoreLayoutModelBinder.cs#L55..L60
In the NextJs SDK there are no warnings (and no strong types).
In the StarterKit there are several components that can use either a page/route field or a specific data source aka component field. That has been solved by using multiple fields and hereby the warning is triggered.
https://github.com/Sitecore/xmcloud-starter-dotnet/blob/main/headapps/aspnet-core-starter/Models/PageContent.cs
I would at least suggest that the out-of-the box configuration should not give a lot of warnings.
It might also be that it would be meaningfull with a binding that solves this fallback scenario (use component field if a data source value but fallback to route field) instead of building the logic in the head application over and over.
The text was updated successfully, but these errors were encountered: