fix: init admin typings and scaffold regressions

[Link2Twenty]

What does it do?

Remove the any from register and update the function so it matches the existing type.
One of the changes is to make App a default export, this is simply to make the linter happy and changing the type might be the correct way to go.

Why is it needed?

Types are good

How to test it?

Load the types in and see the linter is happy.

Related issue(s)/PR(s)

N/A

---

Edit:
I noticed there was already a type the describes this whole export so I've set it up to use that instead.
While I was in there I realised the mapping of translation keys wasn't happening so I've added that in.
Let me know if yo need that to be a send PR.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6735b09

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dosubot]

Related Documentation

Checked 2 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate failed

Failed conditions
54.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[innerdvations]

Thanks for this! I pushed a change that:

• adds regression tests around generated admin templates
• fixes a TS template formatting issue that was producing malformed generated output
• keeps the JS/TS registerTrads behavior aligned
• reverts the App default export change for now to stay consistent with current Strapi docs/examples -- I agree it's probably slightly better but I don't want to add unneccessary friction

If this looks good to you still, I’m happy to merge!

[Link2Twenty]

The reason I changed the export to default was because the addMenuLink type expects it to be a default export. As it stands now it will throw and type error.

addMenuLink: (link: Omit<MenuItem, 'Component'> & {
  Component: () => Promise<{
    default: React.ComponentType;
  }>;
}) => void;

We could fake the import in admin/src/index.ts by wrapping it in an object but it feels a little hoop jumpy

Component: async () => {
  const { App } = await import('./pages/App');

  return {default: App};
},

But other than that everything looks great.