-
Notifications
You must be signed in to change notification settings - Fork 400
Minimum required changes for working tests #481
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
Conversation
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.
Some questions
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 think just one question if we can improve the StreamUtil even better here otherwise this looks really good thanks for the contributions
This pull request has my minimal changes to update the go code generation to the newer go modules. |
…Status condition to validate event monitoring
I'm ok with this at the moment. @galvesribeiro - A second look would be appreciated if you have the time |
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.
Just a few tiny changes and we are good.
Thanks for the contribution! I really appreciate that!
@galvesribeiro Looks like updating Nerbank.GitVersioning package did the trick to compile using 'dotnet build' |
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.
Just one last thing.
Yeah, was about to say that. Github Actions changed the way the variables are added so they had to update the action to support that. 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.
LGTM. Thank you very much for the contribution and your patience!
@jterry75 Its all good to me. Any final thoughts? Otherwise I'll squash and merge to start the release of a new package. |
Next step: I'd like to order and cleanup the code base, applying Roslyn suggestions and removing warnings, to have it tidy and clean before continuing adding pending contributions/functionality. |
Sorry been out. @galvesribeiro - I'm good. Lets merge thanks! |
Minimum required changes for working tests.
Updated models and broken functionality