HaxeFoundation / HaxeFoundation/hx3compat

Remoting server side/client side

Open
#12 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haxe
Stars
17
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Hej !

When an error occurs on server side, remoting often reports me "Class not found " without any class name. I get that as response : "hxrxcy0:g" which means haxe remotin, exception, class, and 0 length string so no class name.
in order to get the real exception that occurs on server side I've changed that line :
https://github.com/HaxeFoundation/hx3compat/blob/master/std/haxe/remoting/HttpConnection.hx#L108 from : `s.serializeException(e);` to `s.serializeException(Std.string(e));`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in std/haxe/remoting/HttpConnection.hx at line 108 and inspect how serializeException encodes the server-side error. Compare the current response with the reported hxrxcy0:g output and the suggested Std.string(e) change. Done means the client receives the server exception details instead of an empty class name, with relevant remoting behavior verified.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.