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
Currently types you write inside your zap file get exported in both the server and client files, this is usually fine. However, I'm pretty nitpicky about separation, and I am not a fan of having my shared files access client files just to access types.
Implementation Details
opt types_output = "src/shared/types/zap.types.luau
This would create a new file in the location specified, and then your server & client would gather the types necessary from there.
The text was updated successfully, but these errors were encountered:
Describe your feature
Currently types you write inside your zap file get exported in both the server and client files, this is usually fine. However, I'm pretty nitpicky about separation, and I am not a fan of having my shared files access client files just to access types.
Implementation Details
opt types_output = "src/shared/types/zap.types.luau
This would create a new file in the location specified, and then your server & client would gather the types necessary from there.
The text was updated successfully, but these errors were encountered: