-
Notifications
You must be signed in to change notification settings - Fork 452
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
add documentation to configuration fields that are not allowed under some circumstances #394
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @sirwindfield . I wanted to help. But I'm not sure about the scope of the PR. If the goal is to conditionally include fields (not only docs) to Maybe I missunderstood the issue and the only intention is to have these fields hidden from the documentation when Let me know if I can help! 😃 |
I think the idea was to use I am not sure if this is still a good idea though user-wise. It would force people to change their config, but I think it's actually good that way. |
Hello @sirwindfield . It seems @CPerezz has not made any progress, but can I help and make a PR? |
I have a PR pending for review. Forgot to link it... Let me do so |
Right, thanks. And great work! 👍 |
is this still open? |
For example:
mixer
,control
anddevice
only apply if the alsa_backend feature is enabled (I think, someone needs to check against this before starting to implement stuff). No idea how to do this in a clean way. Maybe acfg_attr
checking for the feature and only adding the fields to theSharedConfigValues
struct if that is the case.If the above method works, this should actually be a pretty easy enhancement :)
The text was updated successfully, but these errors were encountered: