In this blog post I’ll post about what my plan is for my next 3 releases. As mentioned in my previous release, I want to get started with projects that I have some familiarity with.
For the next couple of releases, I want to hit the ground running and I want to investigate a couple of bugs I have had on my radar for a couple of months.
1. Emmet Bug Fix (https://github.com/Microsoft/vscode/issues/59951)
I found this bug when I was looking through Emmet issues in VSCode. The gist is Emmet has a hard time suggesting the correct abbreviation. In the example given the person submitting was typing in
fsz and was expecting Emmet to give
font-size but instead it gave
font-style. The initial suggestion I had was to fix it was to update the abbreviation from
fsz. This would give the correct the issue but the maintainer suggested this: “in case if it can’t find all characters of abbreviation in snippets, it should match against CSS property names defined in snippets values”. I plan on trying to implement the fix of the course of a couple of weeks.
2. VSCode Bug (https://github.com/Microsoft/vscode/issues/40926)
This bug has to deal with how multi-cursor reacts to inserting on different lines. This one might be a hard one because while it deal with multi-cursor, it also delves deeper into other sections of code I am not as familiar with.
3. VSCode Bug (https://github.com/Microsoft/vscode/issues/64862)
I am thinking about doing this issue that has to deal with adding an option to turn off intelligent multi line paste. The issue is with VSCode not providing a setting to turn it off. The good thing with this bug is that I found the commit where the maintainer made the change(https://github.com/Microsoft/vscode/commit/1374fa6aa7df492b667e5c3c7ffd5e7f025b97e4). With the information, all I need to do is find a way access the setting variables and make the appropriate decision.
Also, I plan on keeping a number of backups in case I can’t make any progress or someone takes one of the bugs in my list above.
VSCode Bug (https://github.com/Microsoft/vscode/issues/64679)
This bug interests me because it has to do with multi-cursor and deals with multi-cursor delete which is not something I have touched yet. The issue occurs when a user tries to use multiple cursors to delete multiple lines. It still leaves multiple cursors behind afterwards and that is not the desired outcome. There was a comment saying he couldn’t replicate which got me worried but I could recreate the second part of the bug but not the first part. I will mainly work on getting the second part working properly and making sure all multi cursors collapse into one cursor.
VSCode Bug (https://github.com/Microsoft/vscode/issues/43238)
The issue in this cause is that VSCode can’t handle a ton of multi-cursors at once. I think it would be a fascinating to investigate this issue and maybe make use of DSA555 and SPO600 to find out if there is a more efficient solution.
VSCode Bug (https://github.com/Microsoft/vscode/issues/56345)
This is a issue with multi select and how when clicking the middle mouse button it captures too much of a selection.
Fast-dna documentation (https://github.com/Microsoft/fast-dna/issues/1165)
I am interested in Fast-dna looking into the documentation would be a good introduction to the project.
I believe these three are a good mix of bugs. I anticipate that the Emmet bug will be the hardest bug to deal with because Emmet is the least familiar project for me. The second issue more is more of a medium level bug fix as it requires me to dig deep and figure out way VSCode is acting like this. Any feedback on my plan would be welcomed.