-
Notifications
You must be signed in to change notification settings - Fork 6
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
Auto-doc yml
s
#35
Draft
james-trayford
wants to merge
71
commits into
docs
Choose a base branch
from
docs-autodoc-yamls
base: docs
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Auto-doc yml
s
#35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Soundfonts, TTS, WIndows Support & Helper functions
update version No.
…ctraliser sonification
Jdaviz modifications
james-trayford
force-pushed
the
docs-autodoc-yamls
branch
from
January 2, 2025 10:28
c7bf7ef
to
06d180f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(CC @SamYoules @soleyhyman @rosedshepherd)
For a while we've been struggling with the best way to document the YAML files - which is key as they contain all the defaults and parameters that people can map their data to - a handy well-formatted reference would be ideal.
@SamYoules found that all the existing solution for YAML => markdown or rst wouldn't work or wouldn't do what we wanted so I've written a script myself as a prototype -
yamls_to_tables.py
running this in the
strauss
environment will print a Markdown representation of the tables which could be output as a file, making use of in the_meta
section docstrings we've been adding. In the_meta
section, I also came up with a syntax for documenting the section and file as a whole. This is demonstrated in the Sampler YAML (src/strauss/presets/sampler/default.yml
) which adds text to the top of the relevant section. All the parameters then get tabulated with their meta string, default value, default ranges and unitsrunning
python yamls_to_tables.py
in thestrauss
top directory will print the markdown which can be copied or piped to clipboard, and displayed in a markdown viewer, e.g. this. If this is viable, I'm hopeful we can add running this script into the documentation generation step, or even get sphinx to run it internally, which would be ideal. Note, github also does a good job rendering markdown, but we don't want to version control the output files of this - instead the documentation can be run on the fly from the existing YAML files.These files I think also make it a lot clearer to see where documentation is missing / insufficient for these parameters so should make finishing up & maintaining the documentation a lot easier.