-
-
Notifications
You must be signed in to change notification settings - Fork 55
fix: correctly infer JSON-serialized types for responses with .toJSON() methods #226
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
Open
aymaneallaoui
wants to merge
4
commits into
elysiajs:main
Choose a base branch
from
aymaneallaoui:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
cf7eb25
feat: enhance type serialization
aymaneallaoui 618a57a
feat: update account response structure
aymaneallaoui ad4a51d
refactor: remove Account class and simplify product response structure
aymaneallaoui 8f9734c
Merge pull request #1 from aymaneallaoui/fix-ddd-serialization-types
aymaneallaoui File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -209,4 +209,4 @@ const app = new Elysia() | |
| }) | ||
| .listen(8080) | ||
|
|
||
| export type Server = typeof app | ||
| export type Server = typeof app | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Treaty HTTP success data now correctly reflects JSON‑serialized shape; ensure errors/rawData are aligned
The change to
data: JSONSerialized<...Awaited<ReturnedType>...>inEdenTreaty.Sign’s HTTP branch aligns Treaty’s success typing with EdenFetch and with the actual JSON on the wire (honoring.toJSON(), Date, function stripping, etc.). This is a welcome fix.As with EdenFetch, the error side still relies on
MapError<Response>, whoseEdenFetchError.valuecurrently uses the raw route response type. If you adopt theMapErrorchange suggested insrc/types.ts(wrappingT[K]inJSONSerialized), Treaty’s error typings will automatically become consistent with these new success semantics.The addition of
rawData: MessageEvent['data']toOnMessage<Data>is useful, but it requires the runtimeEdenWSimplementation (insrc/treaty/index.ts) to actually populaterawDatawhen adaptingMessageEvent(e.g., by passing both parseddataand the originalws.data). It’s worth double‑checking that implementation so type and runtime stay in sync.Also applies to: 26-127, 131-143, 162-165
🏁 Script executed:
Length of output: 1661
I need to check the
parseMessageEventimplementation to confirm whetherrawDatais being properly set at runtime.Let me search the repository directly for the parseMessageEvent implementation.Hmm, I need to check the actual code. Let me revise:
Actually, let me just look at the file directly:
🏁 Script executed:
Length of output: 411
🏁 Script executed:
Length of output: 411
🏁 Script executed:
Length of output: 2289
Runtime does not populate
rawDatafield—MessageEvent.data is overwritten with parsed dataThe type contract at
src/treaty/types.ts:164declaresrawData: MessageEvent['data']as required, but the implementation does not provide it:src/treaty/index.ts:118,parseMessageEvent(ws)returns only the parsed value (seesrc/utils/parsingUtils.ts:66-72){ ...ws, data }at lines 120–123 overwrites the originalws.datawith the parsed resultrawDatais never assignedThis breaks the type contract—calling code cannot safely access
onMessage.rawData(it will beundefined). Either removerawDatafrom the type or update the runtime atsrc/treaty/index.ts:118–123to preserve the original data: