[PR #309] [MERGED] fix warnings when building without any features #711

New issue

Closed

opened 2026-03-02 23:49:29 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 23:49:29 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/aome510/spotify-player/pull/309
Author: @aome510
Created: 12/3/2023
Status: ✅ Merged
Merged: 12/4/2023
Merged by: @aome510

Base: master ← Head: fix-no-default-features-warnings

📝 Commits (1)

34fdad2 fix warnings when building without any features

📊 Changes

4 files changed (+21 additions, -2 deletions)

View changed files

📝 .github/workflows/ci.yml (+7 -1)
📝 spotify_player/src/client/mod.rs (+6 -0)
📝 spotify_player/src/event/mod.rs (+5 -1)
📝 spotify_player/src/main.rs (+3 -0)

📄 Description

fix warnings when building with --no-default-features
update ci.yaml to add a step to check cargo clippy --no-default-features

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/aome510/spotify-player/pull/309 **Author:** [@aome510](https://github.com/aome510) **Created:** 12/3/2023 **Status:** ✅ Merged **Merged:** 12/4/2023 **Merged by:** [@aome510](https://github.com/aome510) **Base:** `master` ← **Head:** `fix-no-default-features-warnings` --- ### 📝 Commits (1) - [`34fdad2`](https://github.com/aome510/spotify-player/commit/34fdad2be4418ae156357b24e4a03439853fe165) fix warnings when building without any features ### 📊 Changes **4 files changed** (+21 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+7 -1) 📝 `spotify_player/src/client/mod.rs` (+6 -0) 📝 `spotify_player/src/event/mod.rs` (+5 -1) 📝 `spotify_player/src/main.rs` (+3 -0) </details> ### 📄 Description - fix warnings when building with `--no-default-features` - update `ci.yaml` to add a step to check `cargo clippy --no-default-features` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>