We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using:
vite build errors out with: ReferenceError [Error]: t is not defined
vite build
ReferenceError [Error]: t is not defined
The enum:
export enum Attending { MAYBE = 'MAYBE', ATTENDING = 'ATTENDING', NOT_ATTENDING = 'NOT_ATTENDING', UNKNOWN = 'UNKNOWN', }
Looking into the generated file & line we can see that after the first enum value t.const is being used instead of __telefunc_t.const
t.const
__telefunc_t.const
shield(addGuest, [__telefunc_t.optional(__telefunc_t.string), { name: __telefunc_t.string, attending: __telefunc_t.or(__telefunc_t.const("UNKNOWN"), t.const("NOT_ATTENDING"), t.const("ATTENDING"), t.const("MAYBE")) }], { __autoGenerated: true });
FYI: Works fine for "normal" typescript enums
The text was updated successfully, but these errors were encountered:
👍 Can you create a reproduction? You can use https://batijs.github.io/ if you want to quickly scaffold a Telefunc app.
Sorry, something went wrong.
Just run npm run build in here: https://stackblitz.com/edit/sveltejs-kit-template-default-lgupus?file=src%2Froutes%2F[slug]%2Fpage.telefunc.ts,src%2Froutes%2F%2Bpage.svelte
npm run build
f57cf11
@louwers Any objections with f57cf11?
@samuba I'll release the fix once Bart gives us the green light.
Fix released in 0.1.57.
0.1.57
In case you can convince your employer: https://github.com/sponsors/brillout.
No branches or pull requests
Using:
vite build
errors out with:ReferenceError [Error]: t is not defined
The enum:
Looking into the generated file & line we can see that after the first enum value
t.const
is being used instead of__telefunc_t.const
FYI: Works fine for "normal" typescript enums
The text was updated successfully, but these errors were encountered: