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
I wanted to drop a feature request to create a new package or add it to the current webview types for the AltV enums. It'd be nice to have things like Vector3, which are shared on AltV also available in the webview types. Right now I have custom converters and such, which is not really nice as those values are shared and should work without a hazzle for a webview.
Would it be possible to have a solution for that discussed? If it's either a package or an include into the webview types.
The text was updated successfully, but these errors were encountered:
why do you need it in webview? you cant create or receive it from clientside there anyway
Does that mean I'm able to include the clientside to the webviews and have functioning types? Wouldn't this conflict/cause issues with possible data given from server side to it? If not, I'll do that instead yea.
Hey there,
I wanted to drop a feature request to create a new package or add it to the current webview types for the AltV enums. It'd be nice to have things like Vector3, which are shared on AltV also available in the webview types. Right now I have custom converters and such, which is not really nice as those values are shared and should work without a hazzle for a webview.
Would it be possible to have a solution for that discussed? If it's either a package or an include into the webview types.
The text was updated successfully, but these errors were encountered: