* build(deps): updates @hey-api/openapi-ts to latest and regenerates APi types * build(deps): updates @hey-api/openapi-ts to latest and regenerates APi types (login) * fix(backoffice): avoid invalid status 0 when synthesizing responses Default to a 500 fallback status when no upstream Response is provided to #createResponse, preventing a RangeError from the Response constructor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * build(deps): updates UmbracoExtension template to @hey-api/openapi-ts 0.97 - Bumps @hey-api/openapi-ts to ^0.97.0 in the extension template. - Simplifies the generate-openapi.js plugin config: spread @hey-api defaults and only override @hey-api/sdk with responseStyle: 'fields' so call sites keep the { data, error } destructuring shape. Removes the redundant @hey-api/client-fetch redeclaration that triggered duplicate-plugin warnings. - Drops the hey-api.ts runtime config file in favour of wiring the generated client through UMB_AUTH_CONTEXT.configureClient() from the entrypoint, so extensions inherit the same auth callback and default response interceptors (401 retry, error notifications) as the core backoffice. - Regenerates the pre-bundled SDK against the template's canonical Umbraco.Extension scaffold so it matches what `npm run generate-client` produces on first run; default hey-api output is flat function exports. - Updates dashboard.element.ts call sites to match the new SDK shape and renames the user model usage to Iuser to follow the new schema. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(git): marks UmbracoExtension template generated SDK as linguist-generated So GitHub diffs collapse the regenerated *.gen.ts files in PRs, matching what we already do for the backoffice client and Login app SDKs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(template): addresses review feedback on PR #22735 - Restores the regenerated SDK's hard-coded baseUrl to https://localhost:44339/ so the SiteDomain template token in the .template.config still substitutes it at scaffold time. The 5443 port leaked in from the local host I used to regenerate; that domain is replaced by the user's chosen SiteDomain on scaffold. - Stops marking onInit as `async`. The UmbEntryPointOnInit signature returns void; making the hook async is harmless under TS's bivariant void-return assignability but is misleading. Kicks the context resolution + client configuration off via .then() and logs a warning when UMB_AUTH_CONTEXT is not present (instead of silently optional-chaining). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(template): keeps onInit async — the framework awaits it The previous tweak was based on Copilot's claim that UmbEntryPointOnInit returns void. The signature does declare void, but the entry-point initializer in app-entry-point-extension-initializer.ts and backoffice-entry-point-extension-initializer.ts both `await moduleInstance.onInit(...)`, so an async onInit is awaited end-to-end. Reverting to async ensures configureClient runs to completion before any element in the extension can hit the API client. --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
21 lines
570 B
JSON
21 lines
570 B
JSON
{
|
|
"name": "umbraco-extension",
|
|
"private": true,
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"watch": "tsc && vite build --watch",
|
|
"build": "tsc && vite build",
|
|
"generate-client": "node scripts/generate-openapi.js https://localhost:44339/umbraco/openapi/umbracoextension.json"
|
|
},
|
|
"devDependencies": {
|
|
"@hey-api/openapi-ts": "^0.97.0",
|
|
"@umbraco-cms/backoffice": "^UMBRACO_VERSION_FROM_TEMPLATE",
|
|
"chalk": "^5.6.2",
|
|
"cross-env": "^10.1.0",
|
|
"node-fetch": "^3.3.2",
|
|
"typescript": "^5.9.3",
|
|
"vite": "^7.3.1"
|
|
}
|
|
}
|