Hey @deckchairlabs,

Thank you for your PR, it seems that the tests don't pass anymore.
Would you mind having a look?

Also, you committed a few changes that seem to be only spacing changes 👉 there is a yarn lint task that you may want to use to clean those out.

Apologies! I rushed this at the end of the day! Wondering how you feel about this change, since it does change behavior, I imagine people updating might have to rename a bunch of imports now.

if this is a breaking change we can only merge it in v4

Thanks for the update 🙏

Indeed, that would change the current behaviour implemented last month.
To sum up:

Current

• Generated file: Generate getSchemaName | DEFAULT
• Imported files: IO Mapping getSchemaName | DEFAULT

Proposed

• Generated file: Generate getSchemaName | DEFAULT
• Imported files: IO Mapping getSchemaName | Generate getSchemaName | DEFAULT

So this would mean that users relying on the generate method with a specific getSchemaName that they don't want to apply for imports would need to update their config file to set an alternative their (i.e. what users currently have to do in reverse).
This concerns users who updated to 3.7.3 and starting using the import handling feature.

I don't have a strong opinion for proposed or current behaviour: I implemented the import handling feature without giving this particular point a thought, as I myself rely on the default in my work 😅