Skip to content
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

Update to the UserListensResponse models to add MBID mapping (No Doc) #24

Merged

Conversation

RustyNova016
Copy link
Contributor

Here is the version without documentation for the MBID Mapping from #22.
It also removes the timerange parameter as it isn't used in the API anymore.

Copy link
Collaborator

@shymega shymega left a comment

Choose a reason for hiding this comment

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

Some nitpicls.

.gitignore Outdated Show resolved Hide resolved
src/raw/client.rs Show resolved Hide resolved
src/raw/client.rs Show resolved Hide resolved
src/raw/response.rs Show resolved Hide resolved
@shymega
Copy link
Collaborator

shymega commented Mar 4, 2024

Also, CI has failed. This needs to be resolved before merge.

@shymega
Copy link
Collaborator

shymega commented Mar 4, 2024

Finally, commits need to be documented a bit more. Currently, they're just one-liners with no justification or detail. The PR desc could be improved too.

Maybe might be worth squashing into one commit too, if it's just for one change.

InputUsername
InputUsername previously approved these changes Mar 4, 2024
InputUsername
InputUsername previously approved these changes Mar 5, 2024
@RustyNova016
Copy link
Contributor Author

Sorry I didn't get to squash those commits while pushing the .gitignore fix. But since it's already approved by one, should it just be done while merging?

@InputUsername InputUsername requested a review from shymega March 6, 2024 21:37
@shymega
Copy link
Collaborator

shymega commented Mar 8, 2024

I would rather the last three commits are squashed into one, rebased against main, and then reworded to describe the changes.

Currently, it'll lead to a somewhat confusing commit history if we merge as-is.

Sorry, I'm not trying to hold up the PR - just trying to keep a easy to understand commit history.

@RustyNova016 RustyNova016 force-pushed the updates/UserListens-nodocs branch from f2f01d3 to 6b35a7c Compare March 8, 2024 09:03
Copy link
Collaborator

@shymega shymega left a comment

Choose a reason for hiding this comment

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

Just one nitpick.

.gitignore Outdated Show resolved Hide resolved
@RustyNova016
Copy link
Contributor Author

Sorry, I was busy all week. Should be good!

@InputUsername InputUsername requested a review from shymega March 25, 2024 22:08
Copy link
Collaborator

@shymega shymega left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the PR - and putting up with my nitpicks!

@InputUsername InputUsername force-pushed the updates/UserListens-nodocs branch from 1bb9d32 to bcb8469 Compare April 2, 2024 15:42
@InputUsername InputUsername merged commit 0ca6c9f into InputUsername:main Apr 2, 2024
1 check passed
@RustyNova016
Copy link
Contributor Author

Neat! Only waiting for the release now.

I'll first work on #25 now that those are merged and I'll go back to adding random stuff that I need

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.

3 participants