asklar / midl-langserv

MIDL 3 language server extension for VS Code

MIDL 3.0 language support

Provides syntax highlighting, autocomplete, and diagnostics for MIDL 3.

Status: Development in progress.

Functionality

• Syntax highlighting
• Basic semantic parsing
• Diagnostics ("squigglies") and context-free auto-completions

This extension collects basic usage telemetry (e.g. which version is being used).

Feedback / bug reports

https://github.com/asklar/midl-langserv

midl-langserv's Issues

Attributes applied to class extends

midl-langserv/server/src/test/assets/interfaces.idl

Lines 14 to 24 in 3bfc735

	// This fails
	// interface IDemoInterface3 requires [PREVIEW_API] IDemoInterface
	// {
	// void DoSomething();
	// }
	// This fails
	// interface IDemoInterface4 requires IDemoInterface, [PREVIEW_API] IGreatDemoInterface
	// {
	// void DoSomething();
	// }

`ref` keyword break syntax highlighting

Describe the bug
When using the ref keyword to use the "fill array" WinRT pattern, syntax highlighting stops working an error is underlined on the declaration of function.

To Reproduce

namespace Foo
{
    runtimeclass Bar
    {
        void Buz(ref UInt8[] arr);
    }
}

Expected behavior
The keyword to be recognized and highlighted as such, with no red squiggles

Screenshots

Versions:

• VSCode: 1.63.2
• MIDL 3 extension: 0.0.26

Additional context
out works as expected.

Wrong description for interface and struct keywords

The attribute and runtimeclass attributes don't even have a description in the auto-completion list.

Add test IDLs

Disable for non-MIDL3 IDL files

Fantastic extension Alex, it's a huge productivity boost.

My project has a mix of MIDL3 and older IDL files. While it's unreasonable to support all the variations of IDL, I wonder if the extension could disable itself on non-MIDL3 files. Currently, the "Problems" pane is polluted with dozens of expected errors as a result.

I don't know if it's super simple to make the difference. In my case, I observe that all non-MIDL3 files either start with:

[uuid(...)]
interface ...

or

cpp_quote("#pragma once")

Or maybe project settings could enable/disable this extension on individual files/directories.

Support for Visual Studio (Not just VSCode!)

Is your feature request related to a problem? Please describe.
Add support for use with Visual Studio (2019+)

Describe the solution you'd like
Extension to support full MIDL syntax highlighting in Visual Studio

Describe alternatives you've considered
Writing my own... :(

Additional context
The support for syntax highlighting of any MIDL code in VS is pretty limited (to the point of being mostly useless) as we use more things based on MIDL3 it would help a LOT if we had a tool that could properly provide syntax highlighting/intellisense.

`typedef` not recognized

Describe the bug
typedef allows to define aliases just like how it works in C. Currently, the extension doesn't recognize this construct and gives an error.

To Reproduce

namespace Foo
{
    typedef Windows.Foundation.EventHandler<Int32> MyEventHandler;

    runtimeclass Foo
    {
        event MyEventHandler MyEvent;
    }
}

Expected behavior
No error, and recognize usages of that typedef later in the same file.

Screenshots

Versions:

• VSCode: 1.63.2
• MIDL 3 extension: v0.0.27