UI5 / UI5/inspector

Feature Request: Models Overview (Models Tab)

Open
#387 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
150
Forks
59
Avg merge
6d 22h
Merged PRs (30d)
2

Description

Hey there,

this feature request is about adding a "Models" tab listing every model on the inspected page. I personally would've loved this feature in plenty situations, especially for applications that're new to me or that I have to quickly take a look at, debug and the like. Just a generally useful thing to have.


I've thought about this feature for a while now and I've usually had some custom copy-paste JS at-hand to do something similar directly in the console but never had the muse or time to actually implement it and add it as feature PR here. I hate to be "that guy" but thanks to LLMs I've had the chance to -relatively - quickly implement the feature locally (or ... let it be implemented, I did spend some tokens ^^), see the PR on my fork here: https://github.com/wridgeu/inspector/pull/1

Why only on the fork? Well it is - so far - fully implemented by AI, so I'd definitely not open a PR with that directly here, no matter how many tokens I throw at it and tests that pass. That aside, opening up a feature request first is just the way to go. :)

Therefore I'd like to have this issue here as official feature request in the hopes that it may be a good addition in the future and might be implemented. Maybe some things could even be taken from the PR. If the feature itself is not worth it, then at least I have it locally. ^^

Rough Feature Outline

  • Shows all models: their data, general infos, metadata (where applicable)
  • Allows direct navigation (on click) to owner element (Control Inspector tab)
  • List is filterable
  • For FE apps it hides internal models by default (configurable)

Overview (Screenshots)

Overview > Data
Image
Overview > Info
Image
Overview > Metadata
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing inspector tabs, especially the Control Inspector tab, and the linked fork implementation. The requested scope is a new Models tab listing model data, info, and metadata, with filtering, navigation to owner elements, and configurable hiding of internal models. Done means these outlined behaviors are implemented and validated in the project.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
devtools, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.