Potential Features to Implement #354
Description
This is a meta issue trying to keep track of some features that are good to have (and open to contribution!).
Improvements
These are relatively isolated improvements that can be done separately in individual PRs.
- Editable data fields in state inspector (related: Edit State Properties in Tree View #74 PR Editable fields #484)
- Improve Vuex state inspector
- Organize information based on modules? (related: show vuex getters per modules #327)
- Move mutation to top, or split state/mutation/getters into tabs? (related: It is really difficult to inspect mutations #301 PR Collapsable and redesigned state inspector #477)
- Easier ways to inspect a component:
- Right click context menu (related: Right click to inspect component #242 PR Right click Inspect component + this.$inspect() #479)
- From code:
this.$inspect()? (PR Right click Inspect component + this.$inspect() #479) -
Auto inspect the component based on inspected DOM node in the Elements panel (PR give the vue dev tool the ablity to select the correspond component w… #469) - Select component in page (picker-style) (PR Select component from dom tree #476)
- Show component file location (and open it in editor on click? this might need build config support) (PR open-in-editor #483)
- Allow inspecting component render function code
- Show component extends hierarchy, could also include mixins applied? (related: visualize extends #337)
- Support ES6 native data structures
Map,Set,WeakMapin data inspector (show structure Set #349) - iFrame support (related: iframe compatibility (Context Menu): RFC #353)
New Panels
These are relatively bigger features that would require discussion, planning and dedicated time frames to implement.
- Route panel (related: Add support for Vue router (adds routing tab) #272)
- Perf panel that profiles component render/patch, computed properties, vuex getters etc...