Reorganising TypeScript interfaces in ScholarX app

Currently, we are facing a problem with our typescript interfaces. Since we are using a modularised project structure we are storing our interfaces like this,

image

The problem with this structure is we are going to multiple interfaces for the same thing cuz the developer doesn’t know whether there’s an interface for this already or not.

The possible fix for this issue is maintaining a single typescript file to store our interfaces without breaking the current project structure.

As we discussed in the stand up we are going to store the response types only. We are going to keep the props types the way it is.

3 Likes

Here’s the issue for this,

2 Likes

Here’s the PR for this above issue: