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

add information on valid file names for source code mirroring #298

Open
gpunktschmitz opened this issue Feb 3, 2024 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@gpunktschmitz
Copy link

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.

@gpunktschmitz gpunktschmitz added the enhancement New feature or request label Feb 3, 2024
@astyled
Copy link
Contributor

astyled commented Feb 3, 2024

Well this double extension is Stylus requirement and probably part of UserCSS spec (if it exists), so I would assume users should know about it.

We can improve import URL placeholder at /import and add an error message to mirror URL placeholder like name/description length check uses.

@gpunktschmitz
Copy link
Author

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.

@astyled
Copy link
Contributor

astyled commented Feb 4, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants