fix(compiler): make name and namespace optional

[tedconn]

Details

Transformation currently throws when not supplied with a name or namespace, we want to lift this restriction when transforming relative imports which currently do not have a namespace.

Does this PR introduce breaking changes?

• ✅ No, it does not introduce breaking changes.

If yes, please describe the impact and migration path for existing applications.

The PR fulfills these requirements:

• Have tests for the proposed changes been added? ✅
• Have you followed these instructions to clearly describe the issue being fixed or feature enhanced? ✅

[tedconn]

This was always the case with CompileOptions

[caridy]

I need to understand this better. Is this a local component? I don't see an example or a test.... I wonder if that's what you're trying to enable.

[tedconn]

@caridy in #1592 we tightened up validation around transformation options and refactored the code and exposed some new types. Now we are seeing that there are cases where name / namespace are not required. For example if I ask the transformer to transform x/foo component then we want to validate those options but if that component has

import a from './a';

then when that file gets transformed, no namespace is passed in.

There is no doubt we need to revisit the rollup plugin and the transformation options, but for now there are hundreds of tests failing in both LWR and LGC because of a missing namespace when it clearly isn't required...

[caridy]

Ok, that makes sense! no further questions from my side!