-
Notifications
You must be signed in to change notification settings - Fork 18
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
Option to declare types with TypeCheck #33
Comments
Hello @jtormey, thanks for the idea! In fact, I talked a little bit about this same idea with @Qqwy at Elixir Conf EU this year as this is something I was also interested in checking out. The only reason I haven't put too much work in that was because I didn't had time to test TypeCheck in depth. What I'd do would be to try out in this library and see what we can do. As far as implementation goes, I am not sure using In the meantime, what are your thoughts on that @dvic? |
Actually, I changed my mind, we are probably better off just using the |
I have also played around with TypeCheck and the library has made great progress since the last time I checked it out. We do plan to use it in some projects so I'm 👍 for the idea. I think using the |
We can make it an optional dependency and using a config option to switch between |
@jtormey opened a PR to start working on that. |
Amazing! That was fast 😄 |
Hey, sorry for being away for a long time. I've been struggling with some aspects of my life in the past few months. I hope that I can come back and contribute again. I'll let you know when I can finally do something for this. |
No worries! Life has been hard for many people. I've been struggling with physical health issues myself the past months. Thank you very much for the heads-up. Take your time, and I wish you all the strength in the world 🫂 ! |
I've been using TypedEctoSchema for a while now and love it, it's been an amazing tool for working with dialyzer!
Now, my team is interested in using type_check to add stricter typing to our project. A hurdle we're running into is that all schemas have their types defined with
typed_schema
, and so cannot easily substitute@type
declarations with@type!
.Is this an option worth adding here? I'm happy to work towards a contribution if so.
The text was updated successfully, but these errors were encountered: