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.

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

chord.parse docs out of date, proposal #29

Open
mrjacobbloom opened this issue Jul 22, 2017 · 0 comments
Open

chord.parse docs out of date, proposal #29

mrjacobbloom opened this issue Jul 22, 2017 · 0 comments

Comments

@mrjacobbloom
Copy link
Contributor

The docs for chord.parse say it returns an Array but it returns an Object.

Speaking of chord.parse, it'd be cool if the returned object contained more granular information about the parsed chord. Right now I'm using tonal in conjunction with another package called chord-magic which does basically the same thing, except its chord parser also gives the following:

  • quality (Major/minor/Augmented/etc)
  • extended (mostly 7ths, I'm not sure if there's a better word for them)
  • suspensions
  • added NCTs
  • overriding root (usually the bottom note of an inversion)

If tonal's chord.parse gave that kind of information I'd only have to depend on one library for chord parsing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant