Repository navigation
WIP: Add implementation for server.url - #6064
GabrielDougherty wants to merge 11 commits into
Conversation
|
the url struct you found it something we shouldn't be using for this; it's our own url parser in zig, which has some advantages in some use cases (doesn't allocate), but it has alot of issues since it wont normalize. another issue of creating a separate generated class here is that any usage of it from js won't be the approach you should take is what you mentioned in the issue: have a binding to JSC ( as a final nit, i think |
|
Ok, I will rework this PR to bind to JSC and implement your other suggestions. |
|
Hi @paperdave, I understand from the Development documentation that if I add Is it absolutely essential for me to get I am making some progress on re-implementing this PR. I think I implemented |
|
Implemented by other PR |
What does this PR do?
This adds a new
urlproperty onserverwhich returns a URL object. That way, the URL object can be passed around instead of the individual fieldsserver.hostnameandserver.port.How did you verify your code works?
I wrote automated tests
If JavaScript/TypeScript modules or builtins changed:
make jsand committed the transpiled changesbun fmt)If Zig files changed: (TODO)
zig fmton the changed filesIf new methods, getters, or setters were added to a publicly exposed class:
If *.classes.ts files were added or changed:
make codegento regenerate the C++ and Zig code