We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are 2 PRs that are already merged.
PR #10 Changed JSON schema validator's options to remove warning: "$ref: key…
PR #8 Added missing 'source' getter on Spec02
Can this 2 fixes be promoted to the npm registry?
Also trunk based development working on master branch seems to be more productive and adopted this days, why not just have 1 branch master?
master
The text was updated successfully, but these errors were encountered:
For anyone hitting the same problem I created a branch with develop merged in master here is what to put in your package.json
package.json
{ "dependencies": { "cloudevents-sdk": "csantanapr/cloudevents-sdk-javascript#tempfix-12", } }
Sorry, something went wrong.
@csantanapr sorry about this little mess!
Now, the things are good again!
https://www.npmjs.com/package/cloudevents-sdk/v/0.2.1
No branches or pull requests
There are 2 PRs that are already merged.
PR #10 Changed JSON schema validator's options to remove warning: "$ref: key…
PR #8 Added missing 'source' getter on Spec02
Can this 2 fixes be promoted to the npm registry?
Also trunk based development working on
master
branch seems to be more productive and adopted this days, why not just have 1 branchmaster
?The text was updated successfully, but these errors were encountered: