ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dilli Dorai <dilli.do...@gmail.com>
Subject REST API code review
Date Thu, 05 Nov 2015 15:26:00 GMT

Would like to suggest some good practice while submitting code review for
REST API changes.

Please include curl calls for success case and failure case and show the
outputs in code review Testing Done section.

This would make it clear what is being addressed and help to get better
code review.

Anyone supporting this suggestion?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message