Skip to content

adding more fields in Request #276

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

Merged
merged 5 commits into from
Nov 28, 2019
Merged

Conversation

marydcouto
Copy link

I need access to set the request status to solved through api. It works only if solved field and its corresponding getters and setters are present in the Request. Create Request API was also failing as priority is mandatory field in the create request API. I also need access to couple of other fields, which I have added in the Request pojo.

aheritier
aheritier previously approved these changes Oct 17, 2018
Copy link
Contributor

@aheritier aheritier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Maybe we should try to add more tests

@marydcouto
Copy link
Author

Please merge the changes, so I can integrate the zendesk request creation in my application. Thanks for approving the changes

@marydcouto
Copy link
Author

Could you please let me know how long will it take to get these changes merged? I am new to public github, so I am not familiar about how things work in public github.

@aheritier
Copy link
Contributor

Hi Mary,

It will take some time. In open-source communities, maintainers aren't active every day and I would prefer to have others reviews because myself I'm not actively using it.
Your changes are looking good when I compare with the documentation but without adding some new tests it is hard to guess if it will be completely fine. This part of the code has sadly a low test coverage : https://github.com/cloudbees/zendesk-java-client/blob/master/src/test/java/org/zendesk/client/v2/RealSmokeTest.java#L609
After the validation of active others developers like @duemir or @johnou you'll have to also wait for a release to grab the new version from maven central.

HTH

@marydcouto
Copy link
Author

I worked on the review comments, but the PR is not getting updated. Can you tell me how to update the pull request?

@marydcouto
Copy link
Author

Changes are done. But the pull request is not getting updated. Could you please tell me what should I do?

@marydcouto
Copy link
Author

Pull request is now showing as updated. Sorry, this is the first time I am raising Pull request in public git hub, so I accidentally sent many comments regarding the pull request. Could you please review now?

Copy link
Contributor

@aheritier aheritier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM WDYT @johnou
The formatting is good now

@johnou
Copy link
Contributor

johnou commented Oct 26, 2018

@aheritier looking better.

@johnou
Copy link
Contributor

johnou commented Oct 26, 2018

@marydcouto can I assume you have tested these changes with your application?

@marydcouto
Copy link
Author

Yes I have tested this code. I made changes for Requests only. I can see 2 tests are failing for createOrganization and deleteOrganization. I am not sure why these tests are failing in my build. Do you know why these tests are failing in my build?

@aheritier aheritier merged commit 1aa9732 into cloudbees-oss:master Nov 28, 2019
@aheritier aheritier added this to the 0.11.0 milestone Nov 28, 2019
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

Successfully merging this pull request may close these issues.

4 participants