Registered a component with a bad importPath, but change is not propagating to generated code

Developer Support
1

I have registered a component with a bad importPath value. That has been fixed, but the change does not propagate and all auto generated components still point to the old importPath. What should be done in cases like that?

2

I already deleted the bad auto generated file but the sync command has recreated it with the wrong import.

3

Hey @lesser_meadowlark! Currently we need to detect the some change in the studio to fix the import.

Here’s an example of how you can fix it

4

We will add an option to fix it directly in the CLI. Sorry about that

5

Thank you! I really appreciate!

6

I noticed that you reloaded the studio in order to propagate the changes. Is this a must every time one changes the code or not always?

7

Just if you are making changes to the code-component meta