-
Notifications
You must be signed in to change notification settings - Fork 517
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
π Wishlist: Users #3901
Comments
I wish for #3861 |
I wish for #454 |
I wish for #266 |
I wish for polkadot-js/apps#10285 (comment) |
I wish for #352 |
I wish for kodadot/nft-gallery#9412 |
I wish for polkadot-js/extension#1268 (comment) |
I wish for #3977 |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-digest-4-apr-2024/7234/1 |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-summit-24-boosting-the-developer-experience/7202/5 |
I wish for #3288 |
I wish for #547 |
I wish for #4090 |
ChaosDAO wishes for #4193 |
I edited to start with this. However, as a human, I'd like to be able to understand what the issue is about without clicking on it (particularly on mobile with no hover preview). This would make for a much better UX going through and voting on these issues. Can we make the bot to recognize and take into account the patern "I wish for [issue-url]" but keep the whole thing human readable still? |
I wish for polkadot-fellows/runtimes#275 |
I wish for use-ink/cargo-contract#1602 |
I wish for polkadot-fellows/RFCs#8 |
Counterpart of #3900
Tracking issues for features that make the life of end-users of the Polkadot platform easier.
Post your opinion by commenting βI wish for
<issue-url>
β (where β<issue-url>
β can be in any repository, not just this) and upvote existing ones by putting a π or π on them.A script will regularly scan the comments with the string pattern above in this issue, and post the leaderboard of the βmost wished featuresβ here.
The text was updated successfully, but these errors were encountered: