You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the change you'd like: when trying to mirror my style from my github project I was unlucky adding my file gpunktstyle.css - searching the github issues of this project I eventually found the valid file names (endings on user.css and user.styl from question #198).
When entering an invalid file name it would be helpful to show the valid file names as hint/error message.
The text was updated successfully, but these errors were encountered:
I was using stylus for years and did not hear/read about it until yesterday. you can create user styles in the browser and on userstyles.world without ever knowing about any extension. why would you not show an appropriate error message when the extension is wrong? or maybe add information on file extension to the faq? https://userstyles.world/docs/faq#how-does-mirroring-source-code-work
I for one had a hard time finding that out.
I agree we need to improve our errors and documentation.
However, I think the root cause here is Stylus implementing "the medium of userstyle" as "Stylus userstyle", not "userstyle file". There's a constant flow of people who don't know they could easily use any version control system (like git) and any text editor/IDE for developing their userstyles, as well as any code sharing platform for publishing it. If they knew it, their experience with userstyles could have been improved a lot.
Describe the change you'd like: when trying to mirror my style from my github project I was unlucky adding my file
gpunktstyle.css
- searching the github issues of this project I eventually found the valid file names (endings onuser.css
anduser.styl
from question #198).When entering an invalid file name it would be helpful to show the valid file names as hint/error message.
The text was updated successfully, but these errors were encountered: