[Woland2k]

Description

Adds the Pricing module's admin UI for the new Vue Admin Shell. With this module and the Admin Shell host installed, price lists, their prices and their assignments can be managed in the new shell, and the product blade shows the product's prices, as in the AngularJS admin.

What the module UI ships:

• Menu entry: "Pricing" (route /pricing, permission pricing:access). It replaces the AngularJS "Pricing" item in the Admin Shell navigation.
• Blades:
  • PricingPricelistList: the workspace. It lists price lists with search, sort, paging and a currency filter; add, delete, export and "Assignments" (all assignments).
  • PricingPricelistDetails: name, currency and description. Widgets: "Prices" and "Assignments", each with a count.
  • PricingPricelistProducts: the products priced in a price list, with the price range of each. "Add" picks products and gives each a zero list price, as AngularJS did; delete and export. Other modules add commands to its toolbar (see below).
  • PricingProductPicker: the product search used by "Add".
  • PricingProductPrices: one product's prices in one price list: list and sale price, minimum quantity and validity dates, checked by the AngularJS price rules (list price set, sale not above list, unique quantity tiers, a price for quantity 1).
  • PricingItemPrices: a product's price lists, with the price range, the number of prices and the catalogs and stores each is assigned to; delete, and pricing the product in another price list.
  • PricingAssignmentList: the assignments of a price list, or all of them; delete, delete all (or all the search matches), export.
  • PricingAssignmentDetails: name, description, price list, store or catalog (exactly one), priority, validity dates, and the "eligible shoppers" conditions from the server's condition types.
• Widgets on other modules' blades: "Prices" on the Catalog module's CatalogProductDetails blade (AngularJS: itemPricesWidget on itemDetail). It shows the price range in the currency with the most prices, evaluated for the product's catalog, and opens PricingItemPrices.
• Extension points:
  • Offered: pricing-pricelist-products-toolbar on PricingPricelistProducts. Other modules add toolbar commands to it with useExtensionPoint("pricing-pricelist-products-toolbar").add(...). Each command gets the price list, the selection, the search keyword, the row count, openBlade and reload. The contract is documented in pricelist-products.vue. The Price export/import module uses it for its CSV commands.
  • Used: the Export module's ExportSettings blade, and its export-filter:<type> extension points for the filter fields of the price list, price and assignment export types. The export commands appear when the Export module's UI is loaded and the user has export:access (as well as pricing:export).
  • Used: the product shared by CatalogProductDetails through its blade context.
• Permissions: the blades and actions follow the server's pricing:access, pricing:read, pricing:create, pricing:update, pricing:delete and pricing:export. "Add" on the price list's products also needs catalog:read or catalog:products:read, because the picker searches the catalog.

How it is built and packaged:

• It is a Module Federation remote (pricing_admin) for the Admin Shell host. It is built from src/VirtoCommerce.PricingModule.Web/vue (yarn build) into src/VirtoCommerce.PricingModule.Web/plugins/admin-shell, and the platform serves it at /modules/$(VirtoCommerce.Pricing)/plugins/admin-shell/. plugin.json there declares the remote and its menu contribution.
• The Web csproj excludes vue/ from the .NET build (Compile, Content, EmbeddedResource and None items), and it copies plugins/** next to the module on dotnet publish. .gitignore ignores the plugins/ build output.
• The UI calls the module's existing REST API through a generated client (vue/src/api_client/virtocommerce.pricing.ts). Its pickers and lists also read the catalog, store, currency and country endpoints, the catalog list entries and products, and the VirtoCommerce.Core.General.Languages setting values.

The AngularJS UI is unchanged. Both UIs use the same endpoints and permissions.

No server change: no schema change, no migrations, no new settings, no new NuGet dependencies.

Companion PRs: VirtoCommerce/vc-module-admin-shell#1 is the host that loads module UIs. VirtoCommerce/vc-shell#386 has the framework fixes that the host's patch carries; this remote runs on the host's shared framework instance.

Languages: the module UI and the module's server texts (setting and permission names, and the AngularJS admin's texts) come in English, Arabic, Hebrew, German, Spanish, Finnish, French, Italian, Japanese, Norwegian, Polish, Portuguese, Russian, Swedish and Chinese. In Arabic and Hebrew the Admin Shell lays the module UI out right to left.

New GraphQL queries and mutations

None. This PR adds no query or mutation.

Changes to existing GraphQL queries and mutations

None. No existing query or mutation changes.

New public services / interfaces / methods

None. No C# code changes. The blade names and the pricing-pricelist-products-toolbar extension point above are the only surface that other Admin Shell module UIs use.

New protected methods (extensibility)

None.

Breaking changes

• Compile time: none. No C# signatures change.
• Package upgrade: none. No published surface is removed or renamed, so no [Obsolete] was needed.
• Runtime behavior: none. The AngularJS admin works as before. The new UI appears only where the Admin Shell host is installed.

New dependencies

• NuGet: none.
• npm (build time only): src/VirtoCommerce.PricingModule.Web/vue/package.json builds the UI with @vc-shell/framework 2.6.3-rc.0 (plus @vc-shell/mf-module, @vc-shell/api-client-generator, vite and vue-tsc). Nothing from it is a NuGet dependency. The package ships only the built bundle in plugins/admin-shell.

Note (product picker): AngularJS opened the Catalog module's item picker, which browses catalogs and categories. This UI has its own flat product search, which also lists variations. The Catalog UI's browse blade has a pick mode, but it cannot pick variations yet; the pickers can move to it once it can.

Note (deleting with an open record): before a delete, the open child blade is asked to close. If it keeps unsaved edits, nothing is deleted. The list detects that through its highlighted row, because the framework's closeChildren() doesn't return whether the children closed.

References

QA-test:

Jira-link:

https://virtocommerce.atlassian.net/browse/VCST-6327

Artifact URL:

https://vc3prerelease.blob.core.windows.net/packages/VirtoCommerce.Pricing_3.1010.0-pr-240-d967.zip
🤖 Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.7% Duplication on New Code

See analysis details on SonarQube Cloud