phero icon indicating copy to clipboard operation
phero copied to clipboard

Full-stack type-safety with pure TypeScript

Results 37 phero issues
Sort by recently updated
recently updated
newest added

I have my project setup with the following folder structure. ``` . ├── clients/ │ ├── app │ ├── web │ └── dashboard └── server ``` While running the `npx...

enhancement

Now a @samen/client will generate a SamenClient with all services of a project. Make it possible to choose which services you want in which clients.

enhancement

All RPC calls are done with the `POST` method. Make it possible to annotate a function with which method the user wants.

enhancement

With the PheroUnchecked utility type, a user can tag a context member to denote that Phero should skip validation for input/output of the middleware/function. Last 2 commits are random improvements...

There are some changes which are not compatible with older versions for TS.

Building further upon #138 (PheroUnchecked), this utility type utilizes PheroUnchecked. When the user adds this to the middleware context Phero will populate the context automatically with the NodeJS' underlying `IncomingMessage`...

I receive the following error when running npx phero when following the getting started guide ![image](https://github.com/user-attachments/assets/b052a972-11e6-4549-a90d-cb2aa7749a38)