This will allow more audio and video files to be played from notebooks or by extensions embedding audio and video into webviews. With this release, the library has been updated to support the following list of codecs and containers. The FFmpeg shared library that ships as part of the VS Code previously had only support for the FLAC codec. Our future work will focus on a separate base view, conflict minification, diffing algorithm refinement, and other improvements. We really appreciate all the feedback we've gotten so far, and more feedback will help us make the merge editor experience great for everyone. If you still find yourself confused by the new merge editor, we would love to hear from you! Please create a new issue in our repo, share a screenshot and your merge editor state (using the Copy Merge Editor State as JSON command). In this release, we focused on the most important UX issues of the merge editor and fixed many bugs. This new algorithm is not optimized for performance yet, but improves the merge editor experience for many edge-cases. A new experimental diffing algorithm can be enabled with the following setting: "mergeEditor.diffAlgorithm" : "experimental" , We started exploring alternative diffing algorithms to improve the quality of conflicts. Colors are used to emphasize the checkboxes for unhandled conflicts. We now make sure that the checkboxes of a conflict are always visible, even when the conflict is larger than the viewport. However, you can switch between the new and old experience at any time and even use them in parallel: When the merge editor opens, you can get the previous experience with a single click in the editor toolbar:īy clicking the same icon next to the file name in the Source Control view, you can skip the merge editor entirely. The old inline conflict decorators are no longer disabled, so the merge editor and inline experience can be used together. The checkboxes can be used to replace the conflict markers with either side, a combination of both sides or, by unchecking them, with base. Instead, the conflict markers remain in the file but are hidden in the result view. VS Code no longer modifies the result file when opening it in the merge editor (conflicting regions were replaced with base). Workbench Merge editor improvements Opening the merge editor from files with conflictsĪ file that has a conflict will now automatically show an Open in Merge Editor button to transition between the text and merge editors. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. If you'd like to read these release notes online, go to Updates on. Markdown Language Server blog post - Learn how Markdown support moved to a Language Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |