onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewSAPUI5 and OpenUI5

New in UI5

7 days30 days90 daysAll time
In the last 7 days
1release122added to the atlas15new pieces of content58revisions
Change: 3
Kind
Origin
Domain
Clear all
181 changes
DayCapability
Change Added to the atlasChange RevisedChange Released

Today
36 changes
audit-summaryadded to the atlasGroups npm audit findings by root dependency, with failing thresholdsCLI,
git-env-branchesadded to the atlasShows which feature branches reached which environment branchCLI,
ui5-task-check-eocpadded to the atlasUI5 build task warning when the app's UI5 version reaches EOCPBuild tool,
Robin van het Hofadded to the atlasPerson,
Show 32 more
Agent access to your codecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something.Capability,
Agent guidancecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field.Capability,
App hostingcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the absence claim about ui5 artifacts.Capability,
Attachmentscoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): drops a count-like contrast with a plugin the flavor does not have.Capability,
Authenticationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no community artifact on the UI5 door provides this capability by an edge; the middlewares the text named provide ui5-build-tooling, and the only sample on the door is not a presence. what_core_does stays, so the core remains present.Capability,
Build and dev-server toolingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): removed a count ("the one ... project") and an absence claim about who built something, restated as a fact about the documentation.Capability,
Change promotioncore coverage, id, ecosystems, name revisedPublic feedback issue #9. The ABAP name is kept in framing_by_ecosystem.abap; the default name and description now state the cross-door concern.Capability,
Custom controls and librariescore coverage revisedReassessed against the graph (check:capabilities): independent maintainers, the abap2UI5 controls and a generator now shape the answer.Capability,
Data bindingcore coverage revisedReassessed against the graph (check:capabilities): states the kinds the independent providers add; the option list names every provider.Capability,
Destinationscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the entry is in the graph, so the name links to it and not to its repository (WRITING section 3.6).Capability,
Document extractioncoverage by ecosystem revisedReassessed against the graph (check:capabilities): removed the provider-count and absence claims (docs/WRITING.md §3); the states are unchanged.Capability,
Documentationcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): absence claims about providers go stale as providers arrive. The flavor states are unchanged.Capability,
Editor supportcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the providers behind the UI5 door are SAP's (UI5 Language Assistant, and SAP Build Code and SAP Web IDE Full-Stack, which serve ui5). The community SAPUI5 Extension is an entry in the graph but has no provides edge to this capability.Capability,
Generatorscore coverage, coverage by ecosystem, framing by ecosystem revisedReassessed against the graph (check:capabilities): the atlas holds these entries, so the links point at them and not at their repositories (docs/WRITING.md section 4).Capability,
Importing and exporting table datacore coverage revisedReassessed against the graph (check:capabilities): the count of sample repositories goes stale as providers arrive, and the ABAP backend importer and the Excel add-in change the shape of the answer, so the note names those kinds. The ABAP state stays core-and-community.Capability,
Input validationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact carries a provides edge to this capability for the UI5 door, because openui5-validator provides ui5-data-binding. The state follows the edges, and the core stays present through the block's sourced what_core_does.Capability,
Integrated frontend dev servercoverage by ecosystem revisedReassessed against the graph (check:capabilities): the only provider of the capability that counts is cds-plugin-ui5, which sits on the CAP door and does not serve the UI5 door, so no provider of another origin counts there. The core stays present on the sourced what_core_does. The middlewares the removed sentence named are not providers of this capability.Capability,
Knowing the maintenance status of a releasecore coverage, coverage by ecosystem revisedui5-task-check-eocp, from public feedback issue #6, is the first independent provider on the UI5 door, beside SAP's SAPUI5 version overview.Capability,
Launchpad and site contentcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed that no community artifact exists, which no longer holds; it now names the kinds the SAP service and the community package add.Capability,
Launchpad pluginscore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed an absence claim and a count of providers (WRITING §3); the flavor states are unchanged.Capability,
LLM integrationcoverage by ecosystem, core coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note claimed who provides the capability behind this flavor, which moves with the corpus. The flavor state is unchanged.Capability,
Localizationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): providers arrived after the block was last looked at, an XLIFF editor and an MCP server among them, and the text named none of the kinds.Capability,
Loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the state is now community-only and the block needed to say what the community adds.Capability,
Seed datacore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact provides seed-data for the UI5 door; the two tools the sentence named provide ui5-testing. The core stays present on the sourced what_core_does. The tools stay on the graph under ui5-testing.Capability,
Server-side renderingcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the sentence claimed an absence of providers, which goes stale when one arrives.Capability,
Task and approval UIscoverage by ecosystem revisedReassessed against the graph (check:capabilities): SAP Task Center (btp-task-center, sap-official) lists ui5 in serves_ecosystems, so the UI5 door has an SAP-official presence; the note also made an absence claim about the graph.Capability,
Themingcore coverage revisedReassessed against the graph (check:capabilities): sap-theming-base-content is an SAP-official package providing this capability, and the core block never named it. State stays core-only: the new providers are SAP-origin.Capability,
Touch operationcore coverage revisedReassessed against the graph (check:capabilities): the community provider's kind was not named in the block; the state stays core-and-community. The web-components flavor history note counts providers by absence and is a dated record, left as written.Capability,
TypeScript supportcore coverage revisedReassessed against the graph (check:capabilities): four providers arrived after the block was assessed (dts-generator task, Babel transform, JSX runtime, UI5 MCP server) and the text named none. The state stays core-and-community: the block's sourced what_core_does keeps the core present and community-origin providers count for the ui5 door. assessed_at and relationship stand.Capability,
UI5 testingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): Node.js unit test environments and mock-data generators are kinds the text did not name.Capability,
Vulnerability scanningecosystems, description revisedPublic feedback issue #10. CAP and UI5 coverage assessed as unmapped: no atlas artifact provides the dependency-tree check there yet.Capability,
Web Components interopcore coverage revisedReassessed against the graph (check:capabilities): providers that arrived after 2026-08-31 and shape the answer were not named. State core-and-community is unchanged.Capability,
Yesterday
1 change
Agent access to your codecoverage by ecosystem revisedRewritten at the maintainer's request (2026-10-25): what SAP ships named whole, and what the community adds written from what its ABAP MCP servers state about how they run, connect and sign in.Capability,
Sat 24
49 changes
btp-agentadded to the atlasLangGraph agent and UI5 chat screen over four BTP MCP serversSample,
aesatirogluadded to the atlasPerson,
alisonjiadded to the atlasPerson,
Amirthaadded to the atlasPerson,
Show 45 more
ankitshah25added to the atlasPerson,
Belle Panadded to the atlasPerson,
Chris Perumaladded to the atlasPerson,
Claire Westadded to the atlasPerson,
denoadded to the atlasPerson,
Denys Severynadded to the atlasPerson,
Eason-Lingadded to the atlasPerson,
elenaylzadded to the atlasPerson,
Felixadded to the atlasPerson,
florianstephan01added to the atlasPerson,
flx-rscadded to the atlasPerson,
Giorgi Cheishviliadded to the atlasPerson,
Harald Gutbrodadded to the atlasPerson,
i307698added to the atlasPerson,
ianquigley-sapadded to the atlasPerson,
IB002added to the atlasPerson,
ilias-gmailadded to the atlasPerson,
Inna Atanasovaadded to the atlasPerson,
Johannes Dobereradded to the atlasPerson,
Justin Wilabyadded to the atlasPerson,
Lena Hammereradded to the atlasPerson,
levwzadded to the atlasPerson,
Luca Mülleradded to the atlasPerson,
Marcos Canales Mayoadded to the atlasPerson,
Mariana Nabokaadded to the atlasPerson,
Mathieu Lajoieadded to the atlasPerson,
matseadded to the atlasPerson,
Michael Henningeradded to the atlasPerson,
msaravanabhavanadded to the atlasPerson,
ᴍᴀʀᴄadded to the atlasPerson,
Ogulcan Kusluogluadded to the atlasPerson,
oksanazubchenkoadded to the atlasPerson,
Paola Lauferadded to the atlasPerson,
Philipp Reisingeradded to the atlasPerson,
PrayasDas03added to the atlasPerson,
Rodrigo Eidelveinadded to the atlasPerson,
Selvakumar Shanmugamadded to the atlasPerson,
SimonStemmleadded to the atlasPerson,
stefanoScalzoadded to the atlasPerson,
Tarang Guptaadded to the atlasPerson,
Vivekadded to the atlasPerson,
ynnenuadded to the atlasPerson,
zhouwei0115added to the atlasPerson,
詹斯迪added to the atlasPerson,
ui5-test-runnerreleased 6.0.0Command line running UI5 QUnit and OPA tests in parallelCLI,
Thu 22
1 change
SRB Consulting Teamadded to the atlasPerson,
Tue 20
26 changes
Adrian Duszyńskiadded to the atlasPerson,
Aydin Ozcanadded to the atlasPerson,
Brianadded to the atlasPerson,
Carlos Orozcoadded to the atlasPerson,
Show 22 more
Codexadded to the atlasPerson,
faustefanadded to the atlasPerson,
Frank Stødleadded to the atlasPerson,
Hasan Çiftçiadded to the atlasPerson,
Herbert Kaintzadded to the atlasPerson,
huschlekadded to the atlasPerson,
Ilja Postnovsadded to the atlasPerson,
Jascha A. Quinternadded to the atlasPerson,
jchirkadded to the atlasPerson,
Joaquim Monserrat Companysadded to the atlasPerson,
Kamil Kováčadded to the atlasPerson,
lenasrdadded to the atlasPerson,
Martín Rodriguezadded to the atlasPerson,
mdel-cmadded to the atlasPerson,
Michael Delladded to the atlasPerson,
nwei-mcadded to the atlasPerson,
osvaldoalvaradodevadded to the atlasPerson,
PulseShiftadded to the atlasPerson,
Raffaele Di Sommaadded to the atlasPerson,
Sergio Graciaadded to the atlasPerson,
Wolfgang Haagadded to the atlasPerson,
ypcycadded to the atlasPerson,
Mon 19
68 changes
@ui5-community/jsx-runtimeadded to the atlasPlugin-based JSX runtime for UI5 views written as .tsxPackage,
@ui5-community/jsx-runtime-helloworldadded to the atlasScaffolded UI5 TypeScript app consuming the JSX runtimeSample,
@ui5-community/jsx-runtime-showcaseadded to the atlasShowcase and documentation app of @ui5-community/jsx-runtimeSample,
@ui5/linteradded to the atlasStatic analysis tool for UI5 projectsCLI,
Show 64 more
@ui5/middleware-code-coverageadded to the atlasUI5 CLI middleware for Istanbul code coverageBuild tool,
@ui5/sample-appadded to the atlasOpenUI5 sample app set up with the UI5 CLISample,
@ui5/tooling-webcadded to the atlasDeprecated UI5 Tooling extensions for UI5 Web Components wrappersBuild tool,
generator-ui5-react-nestadded to the atlasYeoman generator for a UI5 app that loads a React appGenerator,
jest-environment-ui5added to the atlasJest environment running UI5 unit tests in Node.jsPackage,
openui5-error-collectoradded to the atlasUI5 library collecting an app's JavaScript errorsPackage,
openui5-model-json-crudadded to the atlasOpenUI5 JSONModel extension with CRUD over HTTPPackage,
openui5-model-odata-v2-odatapromiseadded to the atlasOpenUI5 OData V2 model extension with PromisesPackage,
openui5-paginatoradded to the atlasA UI5 custom control that pages through large data in a table, for backends that serve pages over REST rather than OData.Package,
openui5-smart-mockserveradded to the atlasUI5 MockServer extension generating mock data with Faker.jsPackage,
openui5-touradded to the atlasOpenUI5 control library for guided app toursPackage,
openui5-validatoradded to the atlasOpenUI5 library validating view fields against JSON schemaPackage,
srbinfoandsupportjsadded to the atlasA JavaScript library that shows a UI5 dialog with application details such as device, resolution, browser zoom, app version and last commit.Package,
srbjsloggeradded to the atlasA browser JavaScript logger whose log, warn and error calls write prominent output to the console, loaded into a UI5 app through index.html or the manifest's resources.Package,
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruptionSample,
UI5 Toolsadded to the atlasVS Code extension to serve, proxy, build and deploy UI5 projectsIDE extension,
ui5-antaresadded to the atlasSAPUI5 library generating OData V2 metadata-based dialogs and pagesPackage,
ui5-cc-timerbuttonadded to the atlasUI5 control library with a button that delays enabling or showingPackage,
ui5-control-generatoradded to the atlasCommand line generator of UI5 custom controls from htmlGenerator,
ui5-deployeradded to the atlasUI5 Tooling module deploying Fiori/UI5 apps to SAP systemsCLI,
ui5-i18n-excel-converteradded to the atlasCLI converting UI5 i18n properties files to Excel and backCLI,
ui5-middleware-destinationadded to the atlasUI5 Tooling middleware proxying destinations and neo-app.json routesBuild tool,
ui5-middleware-oidcadded to the atlasUI5 dev server middleware adding an OpenID Connect loginBuild tool,
ui5-middleware-route-proxyadded to the atlasUI5 server middleware proxying route prefixes to a backendBuild tool,
ui5-space-webcomponent-libraryadded to the atlasUI5 library wrapping a UI5 Web Components package, step by stepSample,
ui5-space-webcomponent-packageadded to the atlasStep-by-step UI5 Web Components package in TypeScriptSample,
ui5-task-cachebuster-indexingadded to the atlasUI5 builder task preparing build output for the cachebusterBuild tool,
ui5-task-dts-generatoradded to the atlasUI5 builder task generating d.ts type declarationsBuild tool,
ui5-task-minifieradded to the atlasUI5 builder task minifying HTML, CSS and JSON filesBuild tool,
ui5-task-transpile-genadded to the atlasUI5 builder task transpiling ES6 to ES5 with BabelBuild tool,
ui5pluginadded to the atlasSAPUI5 extension for Visual Studio CodeIDE extension,
ui5plugin-linteradded to the atlasCommand-line linter for UI5 classes, XML views and i18n filesCLI,
ui5plugin-parseradded to the atlasnpm library parsing SAPUI5 and project UI5 class metadataPackage,
vitest-environment-ui5added to the atlasVitest environment running UI5 unit tests in Node.jsPackage,
vscode-ui5-api-referenceadded to the atlasVS Code side bar view of the SAPUI5 and OpenUI5 API referenceIDE extension,
vscode-ui5-language-assistantadded to the atlasVS Code extension for SAPUI5 and OpenUI5 XML views and manifestIDE extension,
vscode-ui5-odata-mock-generatoradded to the atlasVS Code extension generating OData mock data from service metadataIDE extension,
wdio-qunit-serviceadded to the atlasWebdriverIO service running QUnit test pagesPackage,
Concircleadded to the atlasPerson,
@satiroglu/kaevlinks, type properties, requires revisedThe dependency the entry could not point at before. @ui5/linter is pinned at 1.23.7 in the npm record's dependencies and the README states "Integrates the official @ui5/linter in a restricted child process", so the edge is the maker's own statement; the for sentence carries the conditions the rule reference puts on the adapter rather than on the dependency, which ships with every install. Written now because the artifact exists to point at: it was not in the graph when this entry was drafted, and the prose link in what_it_solves moves from the repository address to the entry with it.CLI,
@ui5-community/jsx-runtimedescription, requires[external:babel-plugin-transform-react-jsx], identity, type properties revisedThe type owns the key for a package (CONCEPT-038) and the record stated nothing, which reads as "does not say" while the README's repository layout says of this package "Publishable to npm." and the package README's install step is "pnpm add @ui5-community/jsx-runtime". The sibling packages in the same monorepo are each marked "Not published" and state no distribution.Package,
app-to-app-nav-bastype properties revisedRevision round against the rules added since the draft was written. The type stays sample, so the edge stays demonstrates: the three modules are companion code to a blog post, not an application published to be deployed. form rests on the root README's one line, read as the same backfill read miyasuta/cap-cross-container's "This project is for the following blog post:". The other keys of the sample type do not exist, and nothing else the sources state asks for a field: the repository names no dependency, no whole it is part of and no flavor beyond the two generators, and the Northwind OData V2 service its descriptors read has no external entry to attach a connects edge to.Sample,
Authenticationecosystems revisedui5-middleware-oidc was staged in intake-20261019-bestofui5 under ui5-build-tooling because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Destinationsecosystems revisedui5-middleware-destination was staged in intake-20261019-bestofui5 under ui5-build-tooling; its drafter left out a destinations edge because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Editor supportecosystems revisedUI5 Language Assistant, SAP's VS Code extension for UI5 XML views and manifest.json, and the SAPUI5 Extension by iljapostnovs were staged in intake-20261019-bestofui5 with this concern as their best fit, and the capability was not open on the UI5 door. The UI5 reading comes from the UI5 Language Assistant README.Capability,
generator-ui5-react-nestentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (main branch) and the npm record for 1.0.14 (Apache-2.0, author Aydin Ozcan, depends on yeoman-generator ^5.7.0). README sentences used: "Unlike traditional solutions that rely on iframes"; "UI5Nest control integration with Workzone or Fiori Launchpad (on-prem) is seamless."; "You can deploy to HTML5 Repository like you do it with your UI5 application."; "The scaffolded React application uses Vite,"; "generator-ui5-react-nest scaffolds the necessary files and configurations for managed router." The when_not_to_use sentence rests on the README's statements that it opts for JavaScript, that react-router-dom is not included in the generated project and that UI5 Web Components are left out.Generator,
Input validationecosystems revisedopenui5-validator was staged in intake-20261019-bestofui5 under ui5-data-binding because this capability was not open on the UI5 door. The UI5 reading comes from the OpenUI5 pages on data types and validation messages.Capability,
Integrated frontend dev serverecosystems revisedThe UI5 dev middlewares staged in intake-20261019-bestofui5 that forward the app's backend paths (ui5-middleware-route-proxy, ui5-middleware-destination) could only be placed under ui5-build-tooling, whose own boundary leaves proxying to a backend to middlewares. The two facets stay on CAP, where they were asked. The UI5 reading comes from the UI5 CLI Server page and SAP's backend-proxy-middleware README.Capability,
Lintingcoverage by ecosystem revisedUI5 linter (@ui5/linter) and ui5plugin-linter were staged in intake-20261019-bestofui5 with provides edges here, so the note that the graph holds no UI5 linter no longer holds and a community linter is present. The UI5 linter README was read again on 2026-10-19.Capability,
Loggingecosystems revisedSRBJSLogger and openui5-error-collector were staged in intake-20261019-bestofui5 with no capability edge, because this capability was not open on the UI5 door. The UI5 reading comes from the sap/base/Log API documentation and the OpenUI5 Logging and Tracing page.Capability,
secondsky/sap-skillstype properties, flavors revisedRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.Skill,
Seed dataecosystems revisedvscode-ui5-odata-mock-generator and openui5-smart-mockserver were staged in intake-20261019-bestofui5 under ui5-testing; the first one's drafter noted that seed-data fit better but was not open on the UI5 door. The UI5 reading comes from the OpenUI5 mock server pages and SAP's ui5-middleware-fe-mockserver README.Capability,
srbinfoandsupportjsentry revisedListed on bestofui5.org and absent from the atlas. The npm description, "A JS library that shows a UI5 dialog with application details such as device, resolution, browser zoom, app version, and last commit.", and the README's manifest.json configuration name the stack. No provides edge: no capability on the UI5 door covers support or diagnostic information.Package,
srbjsloggerentry revisedListed on bestofui5.org and absent from the atlas. Entered on the README's motivation sentence, "I wanted to better separate the log outputs of our UI5 applications" (excerpt), and its UI5 setup steps; the npm description alone, "SRB logging library for javascript", names no stack. No provides edge: the logging capability lists no UI5 door.Package,
UI5 Views, Reimagined: Type-Safe TSX for a Modern Dev Experienceexplains, summary and sources revisedThe session is about the runtime the atlas holds, and the entry named it only as "the incubation project". Its own description gives the project's documentation site as the session's documentation, "Documentation: https://ui5-community.github.io/jsx-runtime/", which is the docs address of artifact:ui5-community-jsx-runtime, and that page carries the same label the session uses for the project, Incubation. The description sentence is added as a source and the summary names and links the runtime instead of pointing at it. The two edges already recorded are unchanged, and so are the claims about what the session shows: the quotes behind them were re-read on 2026-10-19. The session's own repository, github.com/petermuessig/devtoberfest2026-jsxruntime, is named in the same description and is not in the graph, so it is not an edge here.Talk,
ui5-antaresentry revisedListed on bestofui5.org and absent from the atlas. The only UI5-door capability that holds a model-bound form and validation is ui5-data-binding; the odata capability lists no UI5 door, so the OData V2 request side has no edge of its own.Package,
ui5-cc-timerbuttonentry revisedListed on bestofui5.org and absent from the atlas. A UI5 control library packaged for reuse, which is the concern capability:ui5-custom-controls describes.Package,
ui5-fe-mockserver-tutorialtype properties, requires revisedThe README's Prerequisites tell the reader to clone and run that CAP project before starting, and the fact was already in what_it_solves with no edge under it. artifact:marianfoo-ui5-call-action was a pending draft when this entry was written and is published now, so the plain link in the prose became a graph link in the same pass, as did ui5-middleware-odata-recorder.Sample,
ui5-i18n-excel-converterentry revisedListed on bestofui5.org and absent from the atlas. Its README names the UI5 application texts and the webapp/i18n folder, so it passes the scope rule; the one capability on the UI5 door that holds it is localization.CLI,
ui5-tooling-transpiledescription revisedFound while assessing artifact:ui5-community-jsx-runtime, which requires this extension at version 3.12 or later for exactly that option: the record described the transpile step and said nothing about JSX, so the dependency was visible from one side only. The sentence rests on this package's own README, which says of the option that it "includes the `@babel/plugin-transform-react-jsx` into Babels plugin configuration to transform JSX/TSX syntax into JavaScript" (read 2026-10-19). The version the option arrived in is not stated there, so it stays on the requiring edge where the sentence that gives it lives, and nothing here names the runtime, which this README does not mention.Build tool,
ui5pluginentry revisedListed on bestofui5.org as ui5plugin and not yet in the atlas. Read from the repository README and package.json (name ui5plugin, displayName SAPUI5 Extension, version 1.21.1, Apache-2.0, engines vscode ^1.86.0) and the Marketplace page (identifier iljapostnovs.ui5plugin, description "Extension for working with UI5 projects"). The npm name ui5plugin is unpublished, so no npm link. No part_of edge: the README says the extension uses the parser and linter packages, which is a dependency and not a statement that they are parts of it. No capability for editor support on the UI5 door exists, so only linting is claimed.IDE extension,
ui5plugin-linterentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (https://github.com/iljapostnovs/ui5plugin-linter): "Command Line Linter for UI5 based projects."; the install, --rmcache and --format commands; the JS/TS, XML and properties checks; and "It is possible to add config for ui5plugin-parser as well." The npm record for 1.17.1 gives the bin ui5linter, Apache-2.0 and the ui5plugin-parser 1.10.1 dependency. It is a different tool from SAP's UI5 linter (github.com/UI5/linter), which the graph does not hold as an artifact.CLI,
ui5plugin-parserentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (https://github.com/iljapostnovs/ui5plugin-parser): "Parser package for UI5 based projects"; "Initialization process reads the metadata of standard SAPUI5 classes and parses all projects in CWD"; "UIClass will have class metadata such as fields, methods, properties, aggregations, associations, events etc."; "Primarely used by ui5plugin-linter package and Visual Studio Code SAPUI5 Extension"; "nested projects are not supported anymore"; and the npm record for 1.10.1 (Apache-2.0, author Ilja Postnovs). No provides edge: the README describes a parser, and none of the capabilities in the graph is a parsing library. Distribution through npm rests on the registry record alone, since the README gives no install command.Package,
Werkbankprovides revisedWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.Desktop app,
The last 7 days. Older changes stay in each entry's history.
AtomJSON