Bob
I understand what you mean by two way binding.. My question is how are you going to test it without passing variables that are testable? Two way binding is something...
This has to do with Svelte. A way around this would be to utilize a serializing function that converts DOM elements (and their children) into JSON in order to properly...
Recommend looking at this for reference: https://gist.github.com/sstur/7379870
@benmonro Want me to add a couple helper functions based on the above to aide in proper DOM snapshot testing?
The mapping definition cannot be nested under a type [_doc] unless include_type_name is set to true.
Oh man, I jumped the gun a bit. So the issue is actually using Struct::static_ty() in conjunction with Struct::index_mapping(). If I use "mappings": Struct::index_mapping(), it works fine. That will have...
@babichjacob Already done, along with "experimentalDecorators" being set to true. It's doing it for Entities and Resolvers
@babichjacob Sorry, had to create one: https://github.com/MirrorBytes/phorm-kit-vercel I trimmed a bit out, including the database connection.
No need to be sorry! I can't seem to figure out if this is a problem with decorators and metadata in sveltekit or specifically graphql.
@babichjacob So, I moved the graphql implementation to the `api` directory that vercel uses, and changed the function to a vercel centric one. It stills errors. However, if I ditch...
Wait, I lied. This has nothing to do with graphql-helix. It's to do with sveltekit and type reflection, just tried to move it out of the `api` directory, and it's...