Closed aegilops closed 12 months ago
Hi Paul Hodgkinson,
Regarding the TypeScript error you've encountered, this is indeed a known issue. As the project is no longer actively developed, there are a few quirks like this one. MVWA was designed with certain functionalities and features in mind, and these type errors, while present, do not typically interfere with the main operations of the project. The recommended way to use MVWA is in development mode. This mode bypasses these build errors and allows you to explore the project's features. While I understand that running into build issues can be a bit of a hurdle, the project in its current state is best utilised in this way. That being said, contributions to the project are always welcome. If you or anyone else is interested in addressing these issues, it would be greatly appreciated. Any improvements or updates can help make MVWA more robust and user-friendly for everyone.
Now for the particular error with the Navbar component is because of not passing the required arguments. Although it's a straightforward fix, it appears in multiple places. A quick solution could be to modify the Navbar component to accept 'any' type as an argument.
As for the ESLint warnings, they are predominantly present in the frontend code. This is partly due to constrained development time and the complex nature of the type definitions for objects returned by the server. In many cases, I opted to use 'any' to avoid extensive type definitions.
Thanks again for reaching out and for your understanding.
Best, Pulkit Chahar
This failed to build for me.
It gave this TypeScript error, using npm
10.2.2
.There were also numerous type warnings from ESLint: