-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat(codegen): code generator to bootstrap vocab file (#21) #22
feat(codegen): code generator to bootstrap vocab file (#21) #22
Conversation
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
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.
Looks great. Thanks! 🙏
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 npm run build:types
command is failing in the build. Can you look into it, please?
@mttrbrts I investigated the error. Looks like the error is from
It works. But I think these types should be auto-imported. I believe these type declarations are auto-generated using the JSDOC comments? @dselman |
Well spotted @sanketshevkar, I put in a fix here, accordproject/concerto#657 Once that is merged you can update your dependency on the concerto-vocabulary package here, and the build should work. (I tested that locally already). |
Okay got it. Thanks for the fix @mttrbrts 👍 |
Try locally with the unstable package |
@mttrbrts it's working locally. 🙌 |
👍I've published 3.8.2 this evening. |
Signed-off-by: sanketshevkar <shevkar.sanket@gmail.com>
I've made the changes and pushed the code. Locally I've encountered a merge conflict with a snapshot file. I'll fix that and update you. |
Not sure why, this branch shows no conflict with |
Likely your I recommend deleting your local copy of main and checkout again. Otherwise, you can do a hard reset to the upstream branch. |
Yep makes sense. Thanks for merging @mttrbrts. I think I should update the documentation next. |
Documentation for vocabulary code generation |
Closes #21
Changes
Flags
Screenshots or Video
Related Issues
Author Checklist
--signoff
option of git commit.main
fromfork:branchname