-
Notifications
You must be signed in to change notification settings - Fork 5
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
[FEATURES] Add @ module parsing #8
Comments
+1. Without this, I'd feel a bit shit about releasing my modules on hex. |
Actually docs are supported for a while now (and it adds a default undefined doc if not specified), I'm just wanting to support things like moduledoc as well, which shouldn't be too hard, should do that soon..., but documentation is already available on the functions themselves at least. :-) |
|
Nothing else I've noticed :) |
None of the type system related ones seem to work either |
|
Yes, |
That is to say I appreciate the problem with making it all work correctly with dialyzer. That would be nice in the long run, but for now I'd settle for having them visible in my docs :) |
I don't think it's possible to have ex_doc see it and for dialyzer not to see it as I think ex_doc pulls it from the dialyzer type chunk. ^.^; But yeah, I can add the ability to add |
I should probably also add a (Typed this here for future reminding...) |
Ah, I think I wasn't clear. In the protocol itself, I would like to document the expected types of the function so that an implementer may easily understand it. So really the change would just be to copy the type/typep/opaque/spec inside the My time is also quite limited at the moment. This is a 'nice to have' for me, not a blocker so it's likely to be a little while before I can commit time to it also. I'll link an issue about types there to this issue |
Allowing |
I think you're letting perfect be the enemy of workable :) Let me give you an example:
Our simple I personally don't mind too much that dialyzer might generate warnings saying that the types don't match up in the generated module, so long as I can have the types in my documentation. |
Heh, I just need to get some time to do it right, it's not hard, just a touch involved... ^.^ |
Add
@
annotations (like doc and moduledoc and so forth, but stay generic).The text was updated successfully, but these errors were encountered: