-
Notifications
You must be signed in to change notification settings - Fork 14
Ideas for tests #1
Comments
Btw we should make sure the user understands the difference between Bot's suggestions and warnings/errors that need to be fixed. Suggestions can be ignored, warnings/errors not |
Well lets start a list (this is a start) -- feel free to edit this @jimaek
|
|
|
Add Minifed files only please. Easiest is to check for no newlines in the last 99-200 characters. (&/or no newlines after the top-line comment if the file is very short).
I still believe that filenames should be lower-case, but I assume you'll still trump me on this ;) |
|
Yes, that is a common EOF lately. Well skip the last 3 characters then :) I didn't know about Closure's 500-char limit; cheers!
I was thinking more of a soft-warning. Plus jimaek is telling people to at least add minified files, & starting to ask not including non-minifed files. |
"Minified files only" is applied only in a few cases:
In all other cases we host both minified and unminified. So I dont think we need the bot checking for that. It will only add useless information that mods will ignore. I am against lowecase filenames. Some examples why
|
That's a good point.
Where do you get this misinformation from please? https://www.google.com/search?q=windows+util+lowercase |
Im not saying its not possible. But a Windows user is not really used to working with a command line and batch files. There are gui soft for this too but it requires so many extra steps that it makes it too complicated for the user and he will lose all interest. I know the win/unix difference but I really believe its 100x times easier to deal with the rare changes to lowercase by some projects than force all projects to be lowercase at all times. |
Oh good grief; the repo owner is likely using git, lowercase is not more complicated than git for sure. If a non-repo-owner wants to volunteer, then they should at least know how to type. We need to protect the actual users from idiots, not allowing idiots to make more hassles down the road with messy PRs. It's not like lowercase-only is alien: https://github.com/cdnjs/cdnjs#conventions |
cdnjs may have it in their readme but they don't follow it either http://cdnjs.com/libraries/jquery-contextmenu Also when I am talking about users I always mean people that just wanted to help and not actual authors. I know an author wont have any issues to convert his files to lowercase :) If we decided to force lowercase for files it would bring much more problems that it would solve. Most projects using uppercase letters will never switch to lowercase so it will never be an issue. But if we forced it we would simply create problems for ourselves. |
I see what you mean @jimaek but I'd argue that the server should evaluate the lowercase equivalent to the requested uri. http://cdn.jsdelivr.net/tablesorter/2.16.4/js/widgets/widget-staticrow.js should be the same as http://cdn.jsdelivr.net/tablesorter/2.16.4/js/widgets/widget-staticRow.js in my opinion. http://cdn.jsdelivr.net/g/tablesorter(js/widgets/widget-staticRow.js) == http://cdn.jsdelivr.net/g/tablesorter(js/widgets/widget-staticrow.js) Then it would make sense to add a check for the bot to make sure there aren't duplicate files |
I am afraid there is no way to make Nginx case insensitive as it relies on the OS for that. |
For Unix-based OS, it will never never be. Trust me, I had to make a case script 20 years ago when I transferred files from my 8088 DOS computer to a Sun SPARKstation. |
@tomByrer I hope I was able to convince you why its a bad idea to convert everything to lowercase :) |
Your dependency issue is a good point. But that is what I'm trying to also prevent; people used to (become dependent on) mixed/upper cased files. I know you don't like policing too much, but I think this worth spending time to invest in earlier. |
New idea! |
@megawac I left a comment here https://gist.github.com/jsdelivrbot/3c17c9427c31abe15123 |
Validate source maps https://github.com/mattrobenolt/python-sourcemap |
Neat idea, but you'll need the non-minified source files to compare against (which we're trying to prevent uploading) or have the uploader add tests. Most complaints about source maps are they don't exist (we've almost solved that already) & they are not working is that they don't work as intended in the browser because of build steps/engineering (eg early jQuery source maps.) Maybe another solution is to improve reporting via forms, or just let there be enough complaints to warrant the extra code? |
mainfile
parameter should be correct. The file specified should actually exists.I will add more later as more PRs come in and I see the mistakes :)
The text was updated successfully, but these errors were encountered: