Failure handling strategy-9-13.pdf

think of the extension as sub-extensions

i mean what if we made Main UI extension:

• it handles:
  • Walkthroughs
  • views
  • containers

This mean you can think of its as main entry for all related things for UI, with this we can build better system

same goes for the other parts `

• Language servers, debug adapters → Advanced extensions manage their own protocols
• Task providers, problem matchers → Build extensions handle their own systems
• SCM providers → SCM extensions are fully self-contained
• Timeline, comments → Advanced features extensions manage independently
• Search functionality → Search extensions handle their own implementation

`

we need to write requirement file for each component or sub-component like

terminal:

• Should support smart copy to ai model
• Should be concise [just a word of talk, is not real requirement]

we need also to write a development guide for us, for me, how to develop such a big app

a new concept has appeared which is extension pack:

and it means that to avoid Frankenstein problem with extensions, we need to enable something called extension pack, which is grouped extensions proved that is provides good UI/UX

i think this is essential, it is not hard feature but without it you will go Frankenstein with different extensions

we also need to think about Frankenstein problem