#1769 Rename Menas to rest-api - #1781
Conversation
|
I'm not sure how exactly to handle the separation + renaming in README. Any proposals? |
dk1844
left a comment
There was a problem hiding this comment.
I see nothing suspicious -> LGTM (just read the code)
| ____ _____ ____ _____ _ ____ ___ | ||
| | _ \| ____/ ___|_ _| / \ | _ \_ _| | ||
| | |_) | _| \___ \ | |_____ / _ \ | |_) | | | ||
| | _ <| |___ ___) || |_____/ ___ \| __/| | | ||
| |_| \_\_____|____/ |_| /_/ \_\_| |___| | ||
|
|
||
| version ${application.version} |
There was a problem hiding this comment.
While I agree, I would do this
| ____ _____ ____ _____ _ ____ ___ | |
| | _ \| ____/ ___|_ _| / \ | _ \_ _| | |
| | |_) | _| \___ \ | |_____ / _ \ | |_) | | | |
| | _ <| |___ ___) || |_____/ ___ \| __/| | | |
| |_| \_\_____|____/ |_| /_/ \_\_| |___| | |
| version ${application.version} | |
| ____ _____ ____ _____ _ ____ ___ | |
| | _ \| ____/ ___|_ _| / \ | _ \_ _| | |
| | |_) | _| \___ \ | |_____ / _ \ | |_) | | | |
| | _ <| |___ ___) || |_____/ ___ \| __/| | | |
| |_| \_\_____|____/ |_| /_/ \_\_| |___| | |
| Enceladus version ${application.version} |
What do you have in mind specifically?
Then, consider what else must change in the GHP description, what actually public API endpoints to describe (if the time is right?) and publish (in a sense of making them public) them that way. But GHP changes are another story (i.e. PR) anyway. |
| package za.co.absa.enceladus | ||
|
|
||
| package object menas { | ||
| package object restapi { |
There was a problem hiding this comment.
I could not name this package object in tests to rest_api. Hopefully it's not too confusing, given that the module is rest-api and the package is rest_api
There was a problem hiding this comment.
I consider this acceptable.
dk1844
left a comment
There was a problem hiding this comment.
LGTM (just read the code)
|
SonarCloud Quality Gate failed.
|
Brace yourselves, the first part of renaming
Closes #1769