Merged
Conversation
When the JSDoc name for a ManagedObject class differs from its runtime name (as specified in the extend call), then use the JSDoc name to calculate the fully qualified names of generated documentation. Otherwise, JSDoc can't associate the generated documentation with the class. Also enhances the check for a mismatch between documented base type and technical base type. It no longer reports a future error when module:* syntax is used for the documented base type. Cherry-picked from UI5/openui5@1bf4429d4.
…own to the contained APIs Cherry-picked from UI5/openui5@b16b6bcaa.
…nd calls When an extend call creates a class and when the name of the class is known and when the extend call's second argument is an object literal, then ensure that it has a @Lends tag associating the object literal with the class prototype. Also logs a future error when the name of an existing @Lends tags doesn't match the name of the described class. Cherry-picked from UI5/openui5@daab95d89.
Enables automatic discovery and rendering of documentation sections (FAQ, guides, etc.) from directory structure. Sections are discovered at build time and loaded asynchronously at runtime. JIRA: BGSOFUIPIRIN-6925 Cherry-picked from UI5/openui5@c71a404cb.
Parameters of constructors/methods/events, which are of typeDefs are now visualized in DemoKit in expandable Rows of Table: when row is expanded the properties of the typedef are shown in additional rows of the same Table. JIRA: BGSOFUIPIRIN-6935 Cherry-picked from UI5/openui5@1a77603c3.
…for API reference sections Implement support for multi-level section structure in API documentation, allowing sections to contain subsections organized in folder hierarchies. - Sections can now have subsections (e.g., FAQ.md + FAQ/ folder) - Main section content displays as "Overview" subsection - Subsection files automatically loaded from matching directories - Dropdown navigation shows only subsection names, not parent section - The new dynamic sections/subsections are bookmark-able the page automatically scrolls down to the section Example structure: sections/Component/FAQ.md "Overview" subsection sections/Component/FAQ/Example1.md "Example1" subsection sections/Component/FAQ/Example2.md "Example2" subsection JIRA: BGSOFUIPIRIN-6925 Cherry-picked from UI5/openui5@05f6fef35.
7979cc2 to
77649de
Compare
d3xter666
reviewed
Mar 24, 2026
d3xter666
reviewed
Mar 24, 2026
d3xter666
approved these changes
Mar 24, 2026
Member
Author
|
Up-port to V5: UI5/cli#1329 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.