-
Notifications
You must be signed in to change notification settings - Fork 519
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
ToDo: format change #30
Comments
|
Only 1 change from my comparison: 2703 was commented out in master, active in your pastebin Apart from a few other things, I changed the numbers under 0410, not a fan of things like 0410b2, but feel free to change it back or do a mix , or whatever you think is best some of the things Just Me noticed are corrected in my pastebin, but not everything. (only the first 2 I think) |
capital letter? "then also make sure 0806" - My bad, ignore it. I didn't see the comma before "then".
Roman says: use
and then I can just tick rather than edit |
IMO we should always use 0410a, b, c, etc. for "meta"-numbers. It allows for more than just 041[1-9] prefs in one group. EDIT: fe. 0420 could be SB + TP "description only" number, 0421 SB, 0422 TP and 0415 would become 0423 because it applies to both. We would have SB + TP all under 042x that way. |
|
maybe slightly OT, but hear me out ;) I still like the idea of making this overall more modular by using a preferences folder.
If we had multiple files, we could consider using 'pref' instead of 'user_pref' for certain files (fe media) |
IMO it's always good to have an empty newline at EOF |
@Thorin-Oakenpants - I like your writing style and the original user.js. Please don't approve everything and don't change things just for the sake of changing something. Just saying... |
==Roman comments added==
--WTF
I'm sorry, but you said |
testsite: you need to enable |
Just using a new issue to deal with this rather than OT elsewhere.
Here is a pastebin which expires in 24hrs.
Because every single non user_pref line is modified, I have taken the opportunity to do more than that. All up:
[WARNING]
and[SETUP]
The idea, without going overboard, with the
[WARNING]
and[SETUP]
tags is that warning is more about (major) site breaking etc and setup is stuff that is optional or should be looked at when setting up - doh! By that, I mean that 90% of the 270+ numbered items cause zero breakage or issues, 5% are optional i.e the user can make an informed decision and knows the drawbacks (eg keeping history), and the rest are items that cause site breakage or are bad to implement etc. The two tags can be used in conjunction (i.e more than one tag per item), they can be at the end of a section title, at the end of a preference number title, in a comment at the end of a user_pref line, in the middle of a section description, or at the start of a item's warning section etc.@earthlng I have tested it for syntax, etc. Do one of your compares to make sure no pref values got changed, or prefs switched between active/inactive. And then make any changes you want and pastebin me back a version. Make any changes you want (ignore passwords/referrers sections), because this is a one time deal since 70% of the lines are going to change. Take your time.
@everyone else - if you want to proof-read it when you have some time, or offer suggestions, go for it. I can do the commit when we're all happy.
The text was updated successfully, but these errors were encountered: