Support import { m } from '...' on vscode extension

[jeiea]

Background

I'm using paraglidejs with nextjs. To take advantage of the automatic import, I re-exported the contents of message.js, like export * as m from './paraglide/messages'.

Expected behavior

Extension's translation preview should work.

Actual behavior

Don't work.

Additional context

I suspect this line, can you do what the title asks?

[jeiea]

I could achieve this by modifying settings.json modules. I suggest changing the defaults.

[juliomuhlbauer]

Is there some problem using this approach, besides the extension.

[jeiea]

Is there some problem using this approach, besides the extension.

Could you elaborate more? If 'this approach' refers to the * as m syntax, I don't prefer it because it requires additional work:

• I have to manually insert the import statement at the beginning of the file.

  • This can be made easier with snippet configuration, but it requires manual setup and learning.
  • Scrolling for inserting is tedious.

[juliomuhlbauer]

I agree. I thought about the nextjs compiler/paraglide importing all messages. I don't think it is a problem right?

[jeiea]

I don't think it is a problem right?

It's not really a problem but more of a feature request. I'm not suggesting to drop the * as m syntax, but to also support an alternative syntax.

[elron]

I agree, auto importing m isn't easy, I needed to manually go to the docs, search for the import line, copy and paste it into my code.

Auto import would be nice.

I'm using SvelteKit by the way.

[jeiea]

If there are no objections, is it okay to create a PR?

[juliomuhlbauer]

If there are no objections, is it okay to create a PR?

Did you create the PR?

[jeiea]

Not yet.

[jeiea]

I'm currently using i18n-ally for vscode and have lost motivation to continue with this. I'm leaving it open for others.

[juliomuhlbauer]

I'm currently using i18n-ally for vscode and have lost motivation to continue with this. I'm leaving it open for others.

But are you using Paraglide? I think is not supported by the extension

[samuelstroschein]

@jeiea if you do a PR, i'll quickly review and merge it