Broken and incompatible types for inertia render function

[enso-san]

Package version

7.3.0

Describe the bug

Because of the new "type safe" idea for inertia pages and properties its no longer possible using custom and dynamic structures.

I have a big project which has some form of plugins. Each plugin lies in its own folder with own controllers, models and also frontend components.

Now when using the inertia render function the IDE always complains because the page component path is a string, but should be a "never". Also the optional second parameter is required and no longer optional and forces me to use transformers for my page props although those are already strict typed and correctly serialized as im using mongoose schemas for this.

Sadly v7 breaks my whole project and forces me to use additional and absolutely unnecessary code and structures.

Reproduction repo

No response

[thetutlage]

Please share a reproduction repo so I can look into this. Without one I can’t offer any concrete help.​​​​​​​​​​​​​​​​

[enso-san]

Please share a reproduction repo so I can look into this. Without one I can’t offer any concrete help.​​​​​​​​​​​​​​​​

-> https://github.com/enso-san/adonis_bug_5094

This is the default inertia starter kit, just added quick and dirty a controller and component in a non-default location.
Its working as it should, but TS is going mad in the IDE.
See the comments in the test_controller

[enso-san]

@thetutlage Tracked down the problem further...

The indexPages() method in the adonisrc.ts init hook can only run one time. Using it multiple times results in the fact that previous page entries gets overwritten. So its not possible to have vue/inertia pages in multiple different directories. Also the supported frameworks and its glob patterns are hardcoded in inertia/src/index_pages.ts.

So right now, the only way to have page components in different directories is to set the source for indexPages() to the projects uppermost common directory (which in my case results in also indexing components that are no pages).

Another thing i found out: The ExtractProps type in the auto-generated pages file only works when using types or regular primitives as page props. It dont works when its an interface.