Closed Rigellute closed 2 years ago
Some example issues, for different levels:
Rendering of Tickrate and Framerate a bit confusing #626.
We could implement the proposed solution (updating the displayed string formatting). Or perhaps we could create a new cli argument (using clap) to explicitly set an FPS value.
[Feature Request] Hide unplayable songs #718
We can use the spotify API to filter our tracks that are playable or not
Upgrade crates with breaking changes: tui
, rand
, cross-term
.
This one is more involved as it requires some knowledge of the breaking changes and where in spotify-tui
they need fixing.
Pagination of spotify responses is currently handled rather poorly throughout the app. Needing an abstraction to make it easier to work with.
I'd be interested in working on this, I'd be happy to take the unplayable songs issue :) If I finish that I could hop onto other things too!
Im also interested in this. Sounds cool. Have basic Rust knowledge.
Do you have another issue for me where basic rust knowledge is sufficient? Maybe I'll try to upgrade those packages.
I'd be interested here, too. Basic rust knowledge is in place, I'd say.
Project name: spotify-tui Project details: Spotify for the terminal written in Rust
Short bio: I'm the author and maintainer of
spotify-tui
! In my day job, I'm a full stack software engineer building backends/frontends/infra and mobile apps (mostly in Typescript/nodejs/React/React Native/AWS etc.). I've been using Rust for around 3 years in various side projects, and honestly enjoy using Rust more than any other language!Looking for: Basic Rust knowledge is all that's needed to solve a number of issues!
spotify-tui
has grown into a fairly large project but has greatly benefited from contributors of all skill levels. Most contributors (I believe) are fairly new to Rust but have had a large impact in fixing bugs/adding new features.I will post some open issues and try to gauge the level of Rust knowledge required.