-
Notifications
You must be signed in to change notification settings - Fork 147
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
Improve typespecs #121
Improve typespecs #121
Conversation
meta data can be nil. And data and metadata will only be serialized into binary on store.
Postgrex.query/4 has the following typespecs: query(conn(), iodata(), list(), Keyword.t()) :: {:ok, Postgrex.Result.t()} | {:error, Postgrex.Error.t()} So this function would never be called as both return values are handled in the other functions.
Great work, thank you @OleMchls. I'll keep an eye on when you're ready for the PR to be merged. |
@slashdotdash I fixed one warning and ignored the other, so I think this PR is good to be merged. I updated the initial ticket to reflect the current state. Let me know if you have any feedback you would want to see addressed. |
@slashdotdash Together with the incredible 🎉 @coreyhaines I fixed the last remaining build breaker. We also removed the ignored warning and rather had the issue fixed upstream in |
Thanks for taking the time to get this fixed @OleMchls. |
As described in #120 this PR addresses some typespec errors.
Thw work on this triggered two two tickets in their respective repos: sasa1977/fsm#10 & jeremyjh/dialyxir#192
fixes #120
Update 06/14/2018: removed fixed no return error
Update 06/14/2018: update to declare it ready to be merged
Update 06/14/2018: reflect updated fsm