-
Notifications
You must be signed in to change notification settings - Fork 3
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 a new scale #7
Conversation
cardio_crumble.opam
Outdated
@@ -13,8 +13,6 @@ depends: [ | |||
"ocaml" | |||
"dune" {>= "3.3"} | |||
"odoc" {with-doc} | |||
"portmidi" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should go away?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I did not review the rest yet, will take a look maybe later today or this week end! (or @pitag-ha may take a look before!) But this is great, thank you very much!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @Engil !
It seems like I deleted this accidently xD while going through all the files, and checking dependencies etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Engil , just checked, this is weird
When I run,
dune build
It removes portmidi
automatically. Same with cmdliner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha, I am silly!
The dependencies should be added to dune-project
, not the .opam
file.
Dune seems to be handling dependencies by itself, I was not aware of this behaviour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The dependencies should be added to dune-project, not the .opam file. Dune seems to be handling dependencies by itself
We've specified that we want Dune to do so by having (generate_opam_files true)
in the dune-project
.
@AryanGodara, do you want to fix this for us by adding the two dependencies to the dune-project
file (and re-adding them to the .opam
-file)? You could have a look at the dune-project
file of the portmidi library to see the syntax. No pressure! I'm happy to do it myself if you prefer to focus on the scale task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I'd definitely like to work on this issue @pitag-ha !!
Should I open a separate issue for this? Or increase the scope of this current PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change seems trivial in size (although I might get it wrong hehe), so I'll push another commit to this PR for it.
Also, can you please review the code @pitag-ha, when you get the time, since there are no CI checks, I can't tell if I'm moving in the right direction (The code does seem to run, when using --scale=minor
or --scale=pentatonic
, but I'm afraid my ears arent' that trained to catch if it's working properly xd)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I'd definitely like to work on this issue @pitag-ha !!
Nice!
Should I open a separate issue for this? Or increase the scope of this current PR?
I leave that up to you. The cleaner version would be to open a separate PR, merge it, and then rebase this branch over the branch of the other PR. However, as you've said, this change is minimal, so mixing the things here is ok as well. If you think otherwise about git history pedantry, @Engil, let us know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @AryanGodara, this is a great first contribution!
Apart from the few comments I have below (and the one about the dependencies is clearly on us), it looks all good to me to be merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes, @AryanGodara!
@pitag-ha , I've updated the new changes, sorry for the delay! |
Thanks! To be a bit clearer on the dependencies: Given that you're fixing the dependencies in a different PR, this PR should not do any modifications on the |
Yes, I understand the reason @pitag-ha ! |
Signed-off-by: aryan <aryangodara03@gmail.com>
Signed-off-by: aryan <aryangodara03@gmail.com>
Signed-off-by: aryan <aryangodara03@gmail.com>
Signed-off-by: aryan <aryangodara03@gmail.com>
Signed-off-by: aryan <aryangodara03@gmail.com>
Perfect, thank! Yes, that's correct. Once you've gotten rid of the |
Yes, I reverted last commit and rebased with origin/main. Is this PR ready now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the adaptions, @AryanGodara! You're still modifying the .opam
-file. Apart from that LGTM (looks good to me)!
Signed-off-by: aryan <aryangodara03@gmail.com>
Sorry @pitag-ha , removed those two depends |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thanks, @AryanGodara!
Btw, one of these days, I'll try to find time to set up a basic CI checking at least whether the code builds and formats.
Can I try this @pitag-ha ? |
If you know how to do that, that sounds great! What kind of CI infrastructure do you have in mind? You've mentioned Another option could be to use a github actions workflow, making use of And I'm also very happy to hear other suggestions if you have something else in mind. I think in other languages the CI set-up might be more standardized. So, if you were expecting something simpler, don't feel shy to point that out. If you're still happy to work on this, let me know, so that we can open an issue for that and unassign you from #4 for now. |
I was originally thinking of github actions, or googling and seeing how it's usually done. If you install the ocaml-ci , i will research both ways and implement after discussion whichever seems better! It will take a bit of time though, only till sunday, then my exams will be over and i'll work much faster! |
Resolves #3 (May add more scales if this one works properly)
Review needed, not ready yet