progmaweb/docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md, branch feature/remove-xide The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API. Document the ViGet API in full and take zod 4.6.7 for eslint 2026-10-29T09:42:13+00:00 Leitwolf11 2026-10-29T09:42:13+00:00 285e1024da64234b30b0fa425ffd6bf348119db4 The documentation check of the backend found the private members of ViGet/ without a summary and no page for its namespace: - Summaries for every field and helper method of the catalog, the descriptor, the properties reader, publishing and the endpoints. - docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md describes the namespace. - The two regular expressions of TazelPluginDescriptor are excluded from the reference like AccountNamePolicy.CanonicalPattern: the generator replaces their comment with its own. The dependency audit found GHSA for zod < 4.6.6, which can exhaust memory while validating oversized constrained collections. Only eslint-plugin-react-hooks reaches it, and it accepts any zod 4, so an override takes 4.6.7 until the plugin resolves a fixed release itself. pnpm audit --audit-level high finds nothing. 
The documentation check of the backend found the private members of
ViGet/ without a summary and no page for its namespace:
- Summaries for every field and helper method of the catalog, the
  descriptor, the properties reader, publishing and the endpoints.
- docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md describes the
  namespace.
- The two regular expressions of TazelPluginDescriptor are excluded from the
  reference like AccountNamePolicy.CanonicalPattern: the generator replaces
  their comment with its own.

The dependency audit found GHSA for zod < 4.6.6, which can exhaust memory
while validating oversized constrained collections. Only
eslint-plugin-react-hooks reaches it, and it accepts any zod 4, so an
override takes 4.6.7 until the plugin resolves a fixed release itself.
pnpm audit --audit-level high finds nothing.