You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe alternatives you've considered
Merge the frontend and backend repos. But that goes against our direction to decouple teams and reduce merge conflict in the frontend.
Acceptance criteria
The frontend can import backend types from a npm package.
Additional context
In the long-term we can consider exporting a client for frontend to call the backend.
The text was updated successfully, but these errors were encountered:
@VictorDiniz89 sorry we missed you in the team sync today. Are you able to test this feature in the staging environment, or else can you explain how someone else would?
Summary
Having backend types in the frontend will improve integration.
Describe the solution you'd like
Package and publish the generated types in https://github.com/dev-launchers/strapiv4/tree/main/types/generated as a npm package. This can be a GitHub action that publishes every time there is a change in types/generated folder.
Describe alternatives you've considered
Merge the frontend and backend repos. But that goes against our direction to decouple teams and reduce merge conflict in the frontend.
Acceptance criteria
The frontend can import backend types from a npm package.
Additional context
In the long-term we can consider exporting a client for frontend to call the backend.
The text was updated successfully, but these errors were encountered: