Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Add option for exporting zap types into separate file. #77

Open
passhley opened this issue Mar 21, 2024 · 0 comments
Open

[FEAT] Add option for exporting zap types into separate file. #77

passhley opened this issue Mar 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@passhley
Copy link

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.

@passhley passhley added the enhancement New feature or request label Mar 21, 2024
@sasial-dev sasial-dev modified the milestone: 0.7 Release Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants