You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No promise on whether it'll actually be done, but I'm experimenting with adding a best-effort mostly-spec-compliant fetch API to Jint.
I want to write everything the "native" way, instead of using Interop or evaluating javascript strings. So ThingConstructorThingInstanceThingPrototype just like types under Jint.Native.
I experimented with it being an opt-in feature in Jint itself and a standalone project.
The obvious answer to me is just make them public/remove requirement on Realm. Is there anything else I'm missing?
Off topic to the title, I'm slightly leaning towards implementing fetch in Jint as an opt-in feature even if implementing it externally is possible. Would such changes be accepted into the project? Assuming it's implemented well enough, of course.
From #1999 (comment) I'm assuming it's probably yes, but I'd love to hear some opinions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
No promise on whether it'll actually be done, but I'm experimenting with adding a best-effort mostly-spec-compliant
fetchAPI to Jint.I want to write everything the "native" way, instead of using Interop or evaluating javascript strings. So
ThingConstructorThingInstanceThingPrototypejust like types underJint.Native.I experimented with it being an opt-in feature in Jint itself and a standalone project.
For the standalone project:
OrdinaryCreateFromConstructorbut it's set tointernalPrototypeneeds aRealmbut it's set tointernalonEngine(changed in Remove Engine.Realm, expose Engine.Intrinsics and Engine.Global directly #1722 )The obvious answer to me is just make them public/remove requirement on
Realm. Is there anything else I'm missing?Off topic to the title, I'm slightly leaning towards implementing fetch in
Jintas an opt-in feature even if implementing it externally is possible. Would such changes be accepted into the project? Assuming it's implemented well enough, of course.From #1999 (comment) I'm assuming it's probably yes, but I'd love to hear some opinions.
All reactions