[KrzysztofPajak]

Type: bugfix

Issue

<vc:widget> stopped working in every theme and plugin view after #922. In the Nordic theme this is visible on any product page, e.g. /ember-ceramic-pour-over-dripper: the product overview (name, price, add to cart) drops below the picture instead of sitting next to it.

<vc:...> tags are tag helpers that Razor generates at compile time for the view components of every assembly registered with @addTagHelper. WidgetViewComponent lived in Grand.Web. #922 removed @addTagHelper *, Grand.Web from plugin and theme _ViewImports on the assumption that Grand.Web has no tag helpers, and it made a plugin reference to Grand.Web a build error (GRAND001). From then on, Razor emitted <vc:widget> in any plugin or theme view as a literal unknown HTML element, with no build error or warning:

• every widget zone written as <vc:widget> in a theme stopped rendering its widgets. That is the form used throughout the default views, so any view copied from them into a theme is affected.
• in Nordic, the empty <vc:widget> elements inside .nordic-pd__main got width: 100% from Bootstrap's .row > * and pushed the overview column onto a new line.
• for the same reason, Nordic's Simple product layout lost its also-purchased, related, similar and recommended product sections (<vc:products-also-purchased> etc.).

Solution

• WidgetViewComponent moves from Grand.Web to Grand.Web.Common. Every plugin and theme already registers @addTagHelper *, Grand.Web.Common, and Grand.Web.Common is an application part of the host. As a result, <vc:widget> works again in all plugin and theme views without a reference to Grand.Web, and the host views keep working because they register both assemblies. The component's code is unchanged.
• WidgetModel moves along with it. Its namespace stays Grand.Web.Models.Cms, as Move storefront view models into Grand.Web.Models #922 did for the other models. The storefront and theme _ViewImports import that namespace, and WidgetModel was its only type.
• WIDGET_MODEL_KEY moves from CacheKeyConst (Grand.Web) to CacheKey (Grand.Infrastructure). The key string is unchanged and only the component uses it.
• The component's unit tests move to Grand.Web.Common.Tests.
• The product-list components (ProductsAlsoPurchased, RelatedProducts, SimilarProducts, RecommendedProducts) depend on Grand.Web handlers and cannot move. Nordic's Simple layout now invokes them by name with Component.InvokeAsync, as its Grouped layout already did.
• .ai/skills/theme-creation.md explains which <vc:...> tags work in a theme and how to rewrite the others.

Breaking changes

• WidgetViewComponent is now Grand.Web.Common.Components.WidgetViewComponent (was Grand.Web.Components). Views address it by name, so only code that references the type directly is affected.
• CacheKeyConst.WIDGET_MODEL_KEY is now CacheKey.WIDGET_MODEL_KEY.

Testing

1. Build GrandNode.slnx and run the storefront with the Nordic theme active.
2. Open a simple product page, e.g. /ember-ceramic-pour-over-dripper. The name, price and add-to-cart block sit to the right of the gallery, and the related products section appears below the tabs.
3. View the page source of that page and of the home page, a category, /cart and /login: none of them contains <vc:.
4. Activate a widget plugin that renders in a productdetails_* zone (Nordic uses <vc:widget> there) and confirm that it appears on the product page.
5. Switch to the Default theme and repeat steps 2 to 4.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.