VScode extension adding support for IE and Fallout syntaxes.
Post Reply
User avatar
Magus
Site Admin
Posts: 167
Joined: Mon Nov 21, 2016 9:13 am

Roadmap/TODO

Post by Magus » Thu Mar 21, 2019 4:42 am

This a list of possible language server features that may or may not get implemented in BGforge MLS, grouped by priority. The priority is determined by implementation difficulty and demand. Demand is determined by user activity. Things can and will be moved around.

Tier 0: already implemented, but needs community assistance to expand:
1. More highlighting, completion, hovers. Moderately difficult, regexes could be annoying, but mostly this requires dedication to transfer docs to yaml.
2. Snippets. Easy, anyone can add those.

Tier 1: Highly desirable, and supposedly not too hard. This will be focused on first.
1. Context-dependent completion.
2. Incremental text syncronization. Supposedly, that should speed up the other Intellisense features.
3. Autoformat file or selected piece of code. Not easy.
4. Indentation on typing. Should be easy.
5. Support more file formats for errors/warnings reporting (tpa, tpp, baf, d). Waiting for WeiDU update.

Tier 2: Pain/gain = 1/1
1. Signature help. Rudimentarily implemented, needs more community input to expand.
2. Go to definition. And/or declaration (not sure if VScode support the latter).
3. Incremental formatting.

Tier 3: At best situationally helpful, or exceptionally hard, or both. High chance this will never get done.
1. Diagnostics. Not sure if this is needed, in addition to ondemand error reporting.
2. Show all symbol definitions in a document or folder
3. Find all references to a symbol.
4. Highlight all occurences of a symbol

Tier 4: Not even applicable?
1. Show possible actions on errors or warnings
2. Show actionable context information within source code
Please do not PM or email me about my mods and projects. Use forums. Also, see our talk channels.

Post Reply