v2.0.0

Breaking Changes

• Build output folder renamed: gen/cap-js-data-inspector-ui → gen/cap-data-inspector-ui. Any mta.yaml html5 module path, deployment scripts, or @sap/html5-app-deployer configurations pointing at the old folder must be updated.
• MTA module renamed: capjsdatainspectorapp → capdatainspectorapp. After re-running cds add data-inspector, manually remove the old capjsdatainspectorapp html5 module and its artifact entry from your mta.yaml to avoid duplicate/broken deployments.
• UI no longer served by the CAP server for local runs: The SAPUI5 app is no longer served at startup. Run the UI locally with ui5 serve from the generated gen/cap-data-inspector-ui folder (after running cds build). For BTP, deploy via the HTML5 Application Repository service.
• yaml moved from dependency to peerDependency: The yaml package is no longer bundled — consumers must have it available in their project. It is typically present via @sap/cds-dk; if not, add yaml to your devDependencies.

Added

• New config option: cds.data-inspector.authenticationType (xsuaa | ias) to control the approuter authenticationType written into the generated xs-app.json. When not set, it is auto-detected from an existing app/*/xs-app.json and otherwise defaults to xsuaa. The generated xs-app.json no longer hardcodes authenticationType: "xsuaa".
• New config option: cds.data-inspector.odataV4BasePath to set the OData V4 base path used in the generated manifest.json OData service URI, xs-app.json route, and ui5.yaml dev proxy. When not set, it falls back to cds.protocols['odata-v4'].path and then to the default /odata/v4.