-
Notifications
You must be signed in to change notification settings - Fork 29
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
Lidarr API client definition #718
base: new-ui-old
Are you sure you want to change the base?
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.
This is all and good, but I don't think this makes sense right now without the addition of the musicbrainz integration. It's just dead code with no actual use case.
pkg/api/src/infra/arr/lidarr.ts
Outdated
} | ||
} | ||
|
||
export const GetRadarrInstanceFromDb = async ( |
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.
You forgot to rename the function from Radarr to Lidarr
// }, | ||
// ], | ||
// response: ArtistsSchema, | ||
// }, |
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.
Commented out code, shouldn't make it in to the codebase
I should also mention that we follow a strict commit message structure, and that is conventional commits. I'm surprised you were able to commit at all without husky or commit-cli complaining. |
I made the necessary adjustments:
|
The commit messages still does not follow conventional commits. https://www.conventionalcommits.org/en/v1.0.0/ An example would be |
This is one of the first step towards Music integration into Petio.
EDIT:
The following PR is a work in progress. Its final goal is music integration into Petio. Here are tentative tasks (i.e., subject to being edited):