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 release adds a new fusion-lint rule for documenting class fields, fixes a false-positive in the existing single-export-per-file rule, and ships a handful of dev-portal and vite-plugin fixes.
📚 New rule: require-property-tsdoc
@equinor/fusion-framework-lint-config@1.1.0 adds require-property-tsdoc, requiring a preceding TSDoc block comment on class field (property) declarations — including Lit's @property() / @state() decorated fields. private/#name and static fields are exempt, and the rule is included in the recommended preset out of the box.
The framework's own modules were updated to comply: module-analytics, module-app, module-azure-identity, module-bookmark, module-feature-flag, module-http, module-services, fusion-query, and the app-react-router cookbook all gained missing TSDoc comments on flagged class fields.
🐛 Fix: single-export-per-file false positives on @fusionElement
Two false positives in single-export-per-file are fixed:
Barrel files (index.ts, index.tsx, index.mts, index.cts) stay exempt even when a repo's config overrides options.match — previously only the default matcher included the barrel exemption.
A companion top-level const/let that only parameterizes an export default class ... {} (e.g. a tag string used by @fusionElement(tag)) no longer counts as a competing export.
🎨 Dev Portal & Vite Plugins
@equinor/fusion-framework-dev-portal@8.0.3 now matches app-portal's stacking behaviour.
@equinor/fusion-framework-vite-plugin-api-service@2.0.5 includes the HTTP request method in proxy request/response log messages, so multiple requests to the same URL (e.g. GET vs POST) can be distinguished in dev-server logs.
@equinor/fusion-framework-vite-plugin-spa@4.0.15 forwards the original request's cache mode when the service worker re-fetches a proxied request — a caller requesting cache: 'no-store' (e.g. a polling endpoint) no longer silently falls back to the default HTTP cache.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This release adds a new
fusion-lintrule for documenting class fields, fixes a false-positive in the existingsingle-export-per-filerule, and ships a handful of dev-portal and vite-plugin fixes.📚 New rule:
require-property-tsdoc@equinor/fusion-framework-lint-config@1.1.0addsrequire-property-tsdoc, requiring a preceding TSDoc block comment on class field (property) declarations — including Lit's@property()/@state()decorated fields.private/#nameandstaticfields are exempt, and the rule is included in therecommendedpreset out of the box.The framework's own modules were updated to comply:
module-analytics,module-app,module-azure-identity,module-bookmark,module-feature-flag,module-http,module-services,fusion-query, and theapp-react-routercookbook all gained missing TSDoc comments on flagged class fields.🐛 Fix:
single-export-per-filefalse positives on@fusionElementTwo false positives in
single-export-per-fileare fixed:index.ts,index.tsx,index.mts,index.cts) stay exempt even when a repo's config overridesoptions.match— previously only the default matcher included the barrel exemption.const/letthat only parameterizes anexport default class ... {}(e.g. atagstring used by@fusionElement(tag)) no longer counts as a competing export.🎨 Dev Portal & Vite Plugins
@equinor/fusion-framework-dev-portal@8.0.3now matchesapp-portal's stacking behaviour.@equinor/fusion-framework-vite-plugin-api-service@2.0.5includes the HTTP request method in proxy request/response log messages, so multiple requests to the same URL (e.g.GETvsPOST) can be distinguished in dev-server logs.@equinor/fusion-framework-vite-plugin-spa@4.0.15forwards the original request'scachemode when the service worker re-fetches a proxied request — a caller requestingcache: 'no-store'(e.g. a polling endpoint) no longer silently falls back to the default HTTP cache.📦 Released Packages
🔗 Key PRs
require-property-tsdocrule — #5189single-export-per-file@fusionElementfix — #5187🤖 Bip Bop — Release notes assembled by Fusion Assistant. TSDoc for everyone, including your
@property()fields.All reactions