Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`qualified` and `as` in imports are a different color from the `import` keyword

See original GitHub issue

I would’ve expected import, qualified and as to all be formatted as keywords here 😃

Issue Analytics

State:
Created 3 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

rikvdkleijcommented, Sep 26, 2020

Please reopen if still an issue.

1reaction

drathiercommented, Jun 11, 2020

Just trying to be helpful ^^,

Top Results From Across the Web

Using Package Members - Java™ Tutorials

If a member in one package shares its name with a member in another package and both packages are imported, you must refer...

UML Package Import

Elements that become available for use in an importing package through a package import may have a distinct color or be dimmed to...

Import Statements | Qt QML 6.4.1

Importing into a Qualified Local Namespace. The import statement may optionally use the as keyword to specify that the types should be imported...

using directive - C# Reference - Microsoft Learn

The static modifier imports the static members and nested types from a single type rather than importing all the types in a namespace....

Code Packages and Package Imports - Go 101

The importing source files can't use the exported code elements in anonymously imported packages. The purpose of anonymous imports is to initialize the...