Closed simozhan closed 6 years ago
'API rate limit exceeded' Errors. Probably after 1 hour, the retriggering build will be green. And also @xiangge is fixing the 'API rate limit exceeded' in commit https://github.com/product-definition-center/pdc-ruby-gem/pull/45/commits/e7786d0e8f42b01c20f81865ac869c1092ee4fa2 So the patch itself has no errors, adding reviewers anyway.
Rebase the latest codes. And add two more test cases related to reflect and custom class name.
Dear reviewers, any new comments on this patch?
@romanofski About the sensitive info issue, I am thinking maybe we can make the test cases internal and exclude test in gem repo, but let's think about it in another patch :)
@simozhan I don't know... IMHO unless you have a plan it just seems that you push this decision into the future to make a plan. If it's acknowledged as a problem I suppose coming up with a mitigation process would take precedence over adding more features. No?
@romanofski I created a new jira task in PDC-2541. Will deal with it as the next task. I will merge this patch now, that is really a long time, the rpm feature parity somehow waiting on this. We need to make a new gem to continue with other feature parity's task. Sorry about that and thanks for your review comments.
Implement simple has_many association which can help to cache result and add some test cases. As pdc gem only reads data from pdc server, this patch only implement get related association behavior, not including post action.
Known issues:
JIRA: PDC-1685