Skip to content
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.

Sign up for GitHub

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

Jump to bottom

refactor naming: acoustic_mixture_path and acoustic_mixtures #99

Open
christophmluscher opened this issue Oct 6, 2022 · 0 comments
Open

refactor naming: acoustic_mixture_path and acoustic_mixtures #99

christophmluscher opened this issue Oct 6, 2022 · 0 comments
Assignees
@christophmluscher

Comments

@christophmluscher
Copy link
Contributor 

    I noticed an inconsistency...

acoustic_mixture_path and acoustic_mixtures for the same kind of object... I think I introduced that inconsistency...
@michelwi @vieting @JackTemaki @Marvin84 preferences?

Originally posted by @christophmluscher in #92 (comment)
@christophmluscher christophmluscher self-assigned this Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@christophmluscher christophmluscher

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@christophmluscher