ionic-team / ionic-team/demo-ionic-nest-tutorial
Question: SHARED Package
- Dominant language
- TypeScript
- Stars
- 23
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Dear @elylucas , ionic team and community,
thank you very much for this nice tutorial on how to build a backend (with NestJS) and frontend (with Ionic) and the corresponding starter package here. However, i was wondering, if it would be possible to add some kind of shared package (besides the client and server package) that share some common models and interfaces.
Currently, for example, the server has strongly typed classes (e.g., the `Mission`), however, the client does not get this model definition.
On the one hand, this would reduce the need to maintain the same structures on client and server side. On the other, both parts (client & server) would work with / on the same structures. What do you think about this?
All the best
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the existing client and server packages and compare the server's strongly typed Mission class with the corresponding client usage. Decide the scope and package structure for sharing common models and interfaces, then define completion as both sides consuming the shared definitions without duplicated structures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100