Skip to content

Invalid aliased import handled differently than a local import #201

Description

@brekk

What version of Madlib are you running?

0.27.1

How is Madlib installed on your system?

None

What were you trying to do?

import X from "@/MissingFile"

This doesn't yell about the path being invalid

import X from "./MissingFile"

This does yell about the path being invalid

What did you expect to happen?

I want aliases to yell about validity if they can't be resolved

What actually happened?

import X from "@/MissingFile"

X is treated as unused and not invalid.
If you try to access fields on X, that will fail. But the warning indicates we aren't checking validity

Logs

Code Targets

No response

Environment details

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions