Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Package and publish types for frontend to use #204

Closed
chungthuang opened this issue Aug 6, 2024 · 2 comments · Fixed by #210, #220 or #219
Closed

[FEAT] Package and publish types for frontend to use #204

chungthuang opened this issue Aug 6, 2024 · 2 comments · Fixed by #210, #220 or #219
Assignees
Labels

Comments

@chungthuang
Copy link
Contributor

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.

@dbradham
Copy link
Contributor

@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?

@dbradham
Copy link
Contributor

dbradham commented Oct 6, 2024

To test, we can run the same action as GitHub actions from a local machine. (with the same credentials)

@dbradham dbradham mentioned this issue Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment