feat(FormFiledGroupHeaderTitleTextObject): handle export specifier

[adamviktora]

Closes #623

[thatblindgeye]

Couple more things we should do for this:

• The export shouldn't be reliant on the import not being aliased, so we should remove the !importHasAlias` portion of this conditional.
• We only want to make this update if the export is from Patternfly, so we'd need to update line 9 to destructure both the imports and exports, then we want to only make an update in this ExportSpecifier block if an interfaceExport exists.

[adamviktora]

I misunderstood how the exporting can work. I thought it is necessary to first import the name to be able to reexport it, so the codemod only covers a case like this:

import { FormFiledGroupHeaderTitleTextObject } from "@patternfly/react-core";
export { FormFiledGroupHeaderTitleTextObject as HeaderTitleObject };

If I understand your review correctly, we want to cover this:

export { FormFiledGroupHeaderTitleTextObject as HeaderTitleObject } from "@patternfly/react-core";

But shouldn't we still want to have the case above covered by the codemod?

[thatblindgeye]

Ah good point. Yeah we should probably cover both cases then.

[thatblindgeye]

Related to above, for the tests we want the invalid case to be an export from @patternfly...., while a valid case would actually be an export like you have here (not from patternfly)

[adamviktora]

So if I understand, just this:

export { FormFiledGroupHeaderTitleTextObject as TitleTextObject }

should be valid.

But when the import is included:

import { FormFiledGroupHeaderTitleTextObject } from "@patternfly/react-core";
export { FormFiledGroupHeaderTitleTextObject as TitleTextObject };

shouldn't that be invalid? Because if the unaliased import is present, then we know the exported name is 100% the same name we import from Patternfly.