-
Notifications
You must be signed in to change notification settings - Fork 11
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
lib.types does not reveal all types #335
Comments
Hey thanks for opening this issue. If you need any help with the documentation just mention me in the nixpkgs PR. |
I'm glad you're willing to expand in specific cases such as this! types is something I currently have to frequent when working on nixos modules.
i'll be certain to ping when the time comes. there is a lot I can deduce as of right now just by grepping the repo and finding examples uses as i go. The question remains if I should code comment the non function types in preparation for such a feature? |
Documentation for most types is here: |
understood! I'll port them over to be as code comments, or are you able to grab them from their directly for noogle? |
What happened
I'm currently working on adding documentation to lib/types.nix in nixpkgs.
Not all lib.types are shown on noogle.
I assume this is due to limitations of nixdoc?
That being said finding types for use with nixos modules is quite valued.
One other question is should I document the types that are not explicit functions In the interim assuming this may get solved in the future.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected behavior is all types show up even if not functions.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: