User talk:Spratek11

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Welcome to Wikimedia Commons, Spratek11!
Afrikaans | Alemannisch | asturianu | azərbaycanca | Bahasa Banjar | català | čeština | Cymraeg | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | español | Esperanto | euskara | estremeñu | français | Frysk | galego | hrvatski | Bahasa Indonesia | interlingua | Interlingue | íslenska | italiano | Kiswahili | Kurdî | Latina | lietuvių | magyar | Bahasa Melayu | Mirandés | Nederlands | norsk bokmål | occitan | Plattdüütsch | polski | português | português do Brasil | română | rumantsch | Scots | shqip | sicilianu | slovenčina | slovenščina | Basa Sunda | suomi | svenska | Tagalog | Türkçe | vèneto | Tiếng Việt | Zazaki | Ελληνικά | беларуская | беларуская (тарашкевіца)‎ | български | Ирон | македонски | нохчийн | русский | српски / srpski | тоҷикӣ | українська | ქართული | Հայերեն | नेपाली | भोजपुरी | मराठी | हिन्दी | অসমীয়া | বাংলা | தமிழ் | മലയാളം | සිංහල | ไทย | ၽႃႇသႃႇတႆး  | မြန်မာဘာသာ | 한국어 | 日本語 | 中文 | 中文（台灣）‎ | 中文（简体）‎ | 中文（繁體）‎ | 粵語 | עברית | اردو | العربية | تۆرکجه | سنڌي | فارسی | +/−
First steps tutorial

Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content).

You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki.

Getting help

More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump.

Goodies, tips, and tricks
  • Put Babel boxes on your user page so others know what languages you can speak and indicate your graphic abilities.
  • You can find the files you have uploaded in your Uploads.
  • Please sign your name on Talk pages by typing ~~~~.
  • To link to an image page without embedding the image, type: [[:File:Foo.jpg]], which produces: File:Foo.jpg.
  • You may enable gadgets (custom features) for your account.
  • There are several tools to upload files.
  • Have you edited Wikipedia before? This guide might be useful.
Made a mistake?
  • Do you want to have a file renamed or moved? Use the move link and wait for an authorized user to rename it.
  • Do you want to have your recently uploaded picture removed? Tag it as {{speedy|reason here}}. For more information read the deletion guidelines.

-- Wikimedia Commons Welcome (talk) 17:31, 22 July 2017 (UTC)[reply]

A kitten for you![edit]

Jsi skvělý.

Mejdlowiki (talk) 08:49, 18 September 2017 (UTC)[reply]

A goat for you![edit]

You are a goat!

Mejdlowiki (talk) 13:02, 18 September 2017 (UTC)[reply]

Round 2 of Picture of the Year 2017 is open![edit]

You are receiving this message because you voted in R1 of the 2017 Picture of the Year contest, but not yet in R2.

Dear Spratek11,

Wikimedia Commons is happy to announce that the second round of the 2017 Picture of the Year competition is now open. This year will be the twelfth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2017) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. In Round 1, there were 1475 candidate images. There are 58 finalists in Round 2, comprised of the top 30 overall as well as the top 2 from each sub-category.

In the final round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2017.

Round 2 will end on 22 July 2018, 23:59 UTC.

Click here to vote now!

Thanks,
the Wikimedia Commons Picture of the Year committee 11:33, 17 July 2018 (UTC)


Please give images good descriptions[edit]

català ∙ čeština ∙ dansk ∙ Deutsch ∙ English ∙ español ∙ français ∙ galego ∙ italiano ∙ magyar ∙ Nederlands ∙ occitan ∙ polski ∙ português ∙ sicilianu ∙ suomi ∙ македонски ∙ русский ∙ українська ∙ മലയാളം ∙ 日本語 ∙ עברית ∙ العربية ∙ +/−

I noticed you've uploaded [[:{{{1}}}]] and I thought I should draw your attention to a common error.
Please give some thought to writing a good description of uploaded images. This ensures that they can be used. It also helps those that review and improve categories do a better job, which also ensures that images will get used in novel and interesting ways. Thanks, and happy editing!
--Gampe (talk) 14:31, 8 January 2019 (UTC)[reply]

File:Boží muka Tuřany.jpg[edit]

Díky za fotku, ale není zařazena do žádné kategorie a není dostatečně popsána. Tuřany jsou v České republice troje (Brno, Cheb a Kladno). --Gampe (talk) 14:33, 8 January 2019 (UTC)[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 6 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 3 character 1: Expected an identifier and instead saw '<'. - Evidence: <script src="https://ajax.googleapis.com/ajax/libs/d3js/5.7.0/d3.min.js"></script>
  2. ISSUE: line 3 character 2: Missing semicolon. - Evidence: <script src="https://ajax.googleapis.com/ajax/libs/d3js/5.7.0/d3.min.js"></script>
  3. ISSUE: line 3 character 8: Missing semicolon. - Evidence: <script src="https://ajax.googleapis.com/ajax/libs/d3js/5.7.0/d3.min.js"></script>
  4. ISSUE: line 3 character 75: Unclosed regular expression. - Evidence: <script src="https://ajax.googleapis.com/ajax/libs/d3js/5.7.0/d3.min.js"></script>
  5. ISSUE: line 3 character 75: Unrecoverable syntax error. (50% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 12:32, 14 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 3 column 1: Unexpected token <

Your CommonsMaintenanceBot (talk) at 12:32, 14 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 9 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 1 character 1: Expected an identifier and instead saw '#'. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  2. ISSUE: line 1 character 2: Missing semicolon. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  3. ISSUE: line 1 character 2: Expected an identifier and instead saw '#'. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  4. ISSUE: line 1 character 3: Expected an operator and instead saw '<'. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  5. ISSUE: line 1 character 4: Missing semicolon. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  6. ISSUE: line 1 character 10: Missing semicolon. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  7. ISSUE: line 1 character 83: Unclosed regular expression. - Evidence: ##<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
  8. ISSUE: line 1 character 83: Unrecoverable syntax error. (11% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 13:05, 14 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 1 column 1: Unexpected token ILLEGAL

Your CommonsMaintenanceBot (talk) at 13:05, 14 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 7 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 3 character 1: Expected an identifier and instead saw '<'. - Evidence: <!DOCTYPE html>
  2. ISSUE: line 3 character 2: Expected an operator and instead saw '!'. - Evidence: <!DOCTYPE html>
  3. ISSUE: line 3 character 3: Missing semicolon. - Evidence: <!DOCTYPE html>
  4. ISSUE: line 3 character 10: Missing semicolon. - Evidence: <!DOCTYPE html>
  5. ISSUE: line 4 character 1: Expected an identifier and instead saw '<'. - Evidence: <html>
  6. ISSUE: line 4 character 2: Unrecoverable syntax error. (22% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 21:51, 18 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 3 column 1: Unexpected token <

Your CommonsMaintenanceBot (talk) at 21:51, 18 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 6 character 24: Missing semicolon. - Evidence: console.log(htmlObject)

Your CommonsMaintenanceBot (talk) at 15:30, 19 January 2019 (UTC).[reply]


Code issues in User:Spratek11/taglists.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/taglists.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 6 character 24: Missing semicolon. - Evidence: console.log(htmlObject)

Your CommonsMaintenanceBot (talk) at 15:55, 19 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 7 character 12: Missing semicolon. - Evidence: {{universal replace|null|null}}

Your CommonsMaintenanceBot (talk) at 18:13, 19 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 7 column 13: Unexpected identifier

Your CommonsMaintenanceBot (talk) at 18:13, 19 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 19 character 24: Missing semicolon. - Evidence: console.log(htmlObject)

Your CommonsMaintenanceBot (talk) at 08:31, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 20 character 48: Missing semicolon. - Evidence: document.editform.wpSummary.value = htmlObjec

Your CommonsMaintenanceBot (talk) at 08:51, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 16 character 34: Missing semicolon. - Evidence: var name_tit = tit.slice(0,pos-1)

Your CommonsMaintenanceBot (talk) at 21:37, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 28 character 29: Missing semicolon. - Evidence: console.log(htmlObject.data)

Your CommonsMaintenanceBot (talk) at 22:18, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 33 character 34: Missing semicolon. - Evidence: var nazev = images[i].value

Your CommonsMaintenanceBot (talk) at 22:41, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 3 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 11 character 10: Missing semicolon. - Evidence: var exist
  2. ISSUE: line 33 character 34: Missing semicolon. - Evidence: var nazev = images[i].value
  3. ISSUE: line 38 character 20: Missing semicolon. - Evidence: exist = 1
  4. ISSUE: line 40 character 20: Missing semicolon. - Evidence: exist = 0

Your CommonsMaintenanceBot (talk) at 22:47, 20 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 11 character 10: Missing semicolon. - Evidence: var exist
  2. ISSUE: line 34 character 34: Missing semicolon. - Evidence: var nazev = images[i].value
  3. ISSUE: line 39 character 20: Missing semicolon. - Evidence: exist = 1
  4. ISSUE: line 41 character 20: Missing semicolon. - Evidence: exist = 0
  5. ISSUE: line 46 character 76: Missing semicolon. - Evidence: var information_template = (editbox.value).indexOf('{{Information')

Your CommonsMaintenanceBot (talk) at 21:47, 24 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 25 character 99: Missing semicolon. - Evidence: var EdityouURL = 'https://commons.wikimedia.org/w/index.php?title='+ name_tit_res + '&action=edit'

Your CommonsMaintenanceBot (talk) at 07:02, 25 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 25 character 99: Missing semicolon. - Evidence: var EdityouURL = 'https://commons.wikimedia.org/w/index.php?title='+ name_tit_res + '&action=edit'
  2. ISSUE: line 50 character 32: Missing semicolon. - Evidence: var editbox = "zdravim"

Your CommonsMaintenanceBot (talk) at 07:58, 25 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 25 character 99: Missing semicolon. - Evidence: var EdityouURL = 'https://commons.wikimedia.org/w/index.php?title='+ name_tit_res + '&action=edit'
  2. ISSUE: line 50 character 32: Missing semicolon. - Evidence: var editbox = "zdravim"
  3. ISSUE: line 56 character 41: Missing semicolon. - Evidence: var information_template = "kuk"

Your CommonsMaintenanceBot (talk) at 07:59, 25 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 80 character 3: Missing semicolon. - Evidence: })

Your CommonsMaintenanceBot (talk) at 17:57, 25 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 228 character 3: Missing semicolon. - Evidence: })

Your CommonsMaintenanceBot (talk) at 20:37, 28 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 90 character 38: Missing semicolon. - Evidence: mw.config.get('wgAction') === 'edit'

Your CommonsMaintenanceBot (talk) at 19:35, 29 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 105 character 88: Missing semicolon. - Evidence: if ( $( '#editForm' ).length === 0 ){console.log("ano e")} else console.log("ne e"){}

Your CommonsMaintenanceBot (talk) at 20:39, 29 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 105 column 88: Unexpected token {

Your CommonsMaintenanceBot (talk) at 20:39, 29 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 105 character 33: Use '===' to compare with '0'. - Evidence: if ( $( '#editForm' ).length == 0 ){console.log("ano e")} else {console.log("ne e")}

Your CommonsMaintenanceBot (talk) at 20:42, 29 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 105 character 44: Missing semicolon. - Evidence: var e = document.getElementById("editform")

Your CommonsMaintenanceBot (talk) at 21:00, 29 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 106 character 44: Missing semicolon. - Evidence: var e = document.getElementById("editform")
  2. ISSUE: line 109 character 49: Missing semicolon. - Evidence: var id = EdithtmlObject.name ('wpTextbox1')

Your CommonsMaintenanceBot (talk) at 07:08, 30 January 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 8 character 33: Use '===' to compare with '0'. - Evidence: if ( $( '#editForm' ).length == 0 ) return;}
  2. ISSUE: line 21 character 29: Missing semicolon. - Evidence: name_tit = tit.slice(8,pos)
  3. ISSUE: line 51 character 19: Function declarations should not be placed in blocks. Use a function expression or move the statement to the top of the outer function. - Evidence: function doQwikify() {

Your CommonsMaintenanceBot (talk) at 22:58, 2 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 23 character 31: Missing semicolon. - Evidence: var posf = tit.indexOf("File")

Your CommonsMaintenanceBot (talk) at 06:34, 7 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 8 character 34: Use '===' to compare with '0'. - Evidence: if ( $( '#editForm' ).length == 0 ) return;

Your CommonsMaintenanceBot (talk) at 06:53, 7 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 87 character 38: Missing semicolon. - Evidence: var lic = txt_edit.slice(pos_lic)

Your CommonsMaintenanceBot (talk) at 08:40, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 184 character 5: Expected '(end)' and instead saw '}'. - Evidence: });

Your CommonsMaintenanceBot (talk) at 10:01, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 184 column 2: Unexpected token }

Your CommonsMaintenanceBot (talk) at 10:01, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 17 character 129: Missing semicolon. - Evidence: var Overpass = "https://overpass-turbo.eu/?w=%22image%22%3D%22File%3AK%C5%99%C3%AD%C5%BE+na+ulici+Bystrck%C3%A1.jpg%22+global&R"

Your CommonsMaintenanceBot (talk) at 12:04, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 191 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  2. ISSUE: line 197 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {

Your CommonsMaintenanceBot (talk) at 18:10, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 192 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  2. ISSUE: line 199 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module2){
  3. ISSUE: line 209 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {

Your CommonsMaintenanceBot (talk) at 20:26, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 192 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  2. ISSUE: line 199 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module2){
  3. ISSUE: line 200 character 40: Bad or unnecessary escaping. - Evidence: console.log(name+"\ahoj/"+key+":"+module2[key]);
  4. ISSUE: line 209 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {

Your CommonsMaintenanceBot (talk) at 20:33, 8 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 192 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module1){
  2. ISSUE: line 198 character 26: 'name' is already defined. - Evidence: for(var name in OverpassObject.elements){
  3. ISSUE: line 200 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 207 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module2){
  5. ISSUE: line 208 character 40: Bad or unnecessary escaping. - Evidence: console.log(name+"\ ahoj/"+key+":"+module2[key]);
  6. ISSUE: line 217 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {

Your CommonsMaintenanceBot (talk) at 00:13, 9 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 186 character 18: Use '!==' to compare with '0'. - Evidence: if (Overpass != 0){
  2. ISSUE: line 200 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 214 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 225 character 22: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  5. ISSUE: line 227 character 27: 'value' is already defined. - Evidence: var value = tagso[key];
  6. ISSUE: line 237 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  7. ISSUE: line 239 character 19: 'value' is already defined. - Evidence: var value = OverpassObject[key];

Your CommonsMaintenanceBot (talk) at 12:13, 11 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 134 character 22: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  2. ISSUE: line 145 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  3. ISSUE: line 150 character 22: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  4. ISSUE: line 152 character 27: 'value' is already defined. - Evidence: var value = tagso[key];
  5. ISSUE: line 159 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  6. ISSUE: line 161 character 31: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  7. ISSUE: line 177 character 5: Expected '(end)' and instead saw '}'. - Evidence: });

Your CommonsMaintenanceBot (talk) at 14:56, 11 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 177 column 2: Unexpected token }

Your CommonsMaintenanceBot (talk) at 14:56, 11 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 24 character 17: Missing semicolon. - Evidence: var Overpass
  2. ISSUE: line 205 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 219 character 23: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 230 character 22: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  5. ISSUE: line 232 character 27: 'value' is already defined. - Evidence: var value = tagso[key];
  6. ISSUE: line 242 character 18: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  7. ISSUE: line 244 character 19: 'value' is already defined. - Evidence: var value = OverpassObject[key];

Your CommonsMaintenanceBot (talk) at 17:06, 11 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 8 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 138 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  2. ISSUE: line 149 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  3. ISSUE: line 158 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ['id'] = module[key];
  4. ISSUE: line 159 character 80: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem['id']);
  5. ISSUE: line 159 character 87: Expected a 'break' statement before 'case'. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem['id']);
  6. ISSUE: line 162 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ['lat'] = module[key];
  7. ISSUE: line 163 character 81: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem['lat']);
  8. ISSUE: line 163 character 89: Expected a 'break' statement before 'case'. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem['lat']);
  9. ISSUE: line 165 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ['lon'] = module[key];
  10. ISSUE: line 166 character 81: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem['lon']);
  11. ISSUE: line 172 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  12. ISSUE: line 174 character 35: 'value' is already defined. - Evidence: var value = tagso[key];
  13. ISSUE: line 181 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  14. ISSUE: line 183 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];

Your CommonsMaintenanceBot (talk) at 08:31, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 139 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 150 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 160 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ['id'] = module[key];
  5. ISSUE: line 161 character 80: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem['id']);
  6. ISSUE: line 164 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ['lat'] = module[key];
  7. ISSUE: line 165 character 81: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem['lat']);
  8. ISSUE: line 168 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ['lon'] = module[key];
  9. ISSUE: line 169 character 81: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem['lon']);
  10. ISSUE: line 176 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  11. ISSUE: line 178 character 35: 'value' is already defined. - Evidence: var value = tagso[key];
  12. ISSUE: line 185 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  13. ISSUE: line 187 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];

Your CommonsMaintenanceBot (talk) at 08:43, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 4 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 143 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ["id"] = module[key];
  5. ISSUE: line 144 character 81: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"]);
  6. ISSUE: line 144 character 88: Expected a 'break' statement before 'case'. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"]);
  7. ISSUE: line 147 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ["lat"] = module[key];
  8. ISSUE: line 148 character 82: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"]);
  9. ISSUE: line 148 character 90: Expected a 'break' statement before 'case'. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"]);
  10. ISSUE: line 150 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ["lon"] = module[key];
  11. ISSUE: line 151 character 82: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"]);
  12. ISSUE: line 157 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  13. ISSUE: line 159 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  14. ISSUE: line 167 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  15. ISSUE: line 169 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  16. ISSUE: line 213 character 98: Missing semicolon. - Evidence: console.log("Overpass_elem = " + index + " - " +" - "+ names +" - "+ element)

Your CommonsMaintenanceBot (talk) at 10:18, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 143 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ["id"] = module[key];
  5. ISSUE: line 144 character 81: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  6. ISSUE: line 144 character 88: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  7. ISSUE: line 147 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ["lat"] = module[key];
  8. ISSUE: line 148 character 82: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  9. ISSUE: line 148 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  10. ISSUE: line 151 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ["lon"] = module[key];
  11. ISSUE: line 152 character 82: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  12. ISSUE: line 152 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  13. ISSUE: line 159 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  14. ISSUE: line 161 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  15. ISSUE: line 169 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  16. ISSUE: line 171 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  17. ISSUE: line 215 character 98: Missing semicolon. - Evidence: console.log("Overpass_elem = " + index + " - " +" - "+ names +" - "+ element)

Your CommonsMaintenanceBot (talk) at 10:27, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 143 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ["id"] = module[key];
  5. ISSUE: line 144 character 81: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  6. ISSUE: line 144 character 88: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  7. ISSUE: line 147 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ["lat"] = module[key];
  8. ISSUE: line 148 character 82: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  9. ISSUE: line 148 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  10. ISSUE: line 151 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ["lon"] = module[key];
  11. ISSUE: line 152 character 82: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  12. ISSUE: line 152 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  13. ISSUE: line 159 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  14. ISSUE: line 161 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  15. ISSUE: line 169 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  16. ISSUE: line 171 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  17. ISSUE: line 197 character 71: Missing semicolon. - Evidence: console.log("Overpass_elem.length = " + Overpass_elem.length)
  18. ISSUE: line 219 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 11:01, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 143 character 43: ['id'] is better written in dot notation. - Evidence: Overpass_elem ["id"] = module[key];
  5. ISSUE: line 144 character 81: ['id'] is better written in dot notation. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  6. ISSUE: line 144 character 88: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem ["id"])
  7. ISSUE: line 147 character 43: ['lat'] is better written in dot notation. - Evidence: Overpass_elem ["lat"] = module[key];
  8. ISSUE: line 148 character 82: ['lat'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  9. ISSUE: line 148 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem ["lat"])
  10. ISSUE: line 151 character 43: ['lon'] is better written in dot notation. - Evidence: Overpass_elem ["lon"] = module[key];
  11. ISSUE: line 152 character 82: ['lon'] is better written in dot notation. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  12. ISSUE: line 152 character 90: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem ["lon"])
  13. ISSUE: line 159 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  14. ISSUE: line 161 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  15. ISSUE: line 169 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  16. ISSUE: line 171 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  17. ISSUE: line 197 character 71: Missing semicolon. - Evidence: console.log("Overpass_elem.length = " + Overpass_elem.length)
  18. ISSUE: line 198 character 25: ['id'] is better written in dot notation. - Evidence: if(Overpass_elem["id"] !== null){
  19. ISSUE: line 219 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 11:03, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 144 character 85: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem [0])
  5. ISSUE: line 148 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem [1])
  6. ISSUE: line 152 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem [2])
  7. ISSUE: line 160 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  8. ISSUE: line 162 character 39: Missing semicolon. - Evidence: var ii = 4
  9. ISSUE: line 163 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  10. ISSUE: line 173 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  11. ISSUE: line 175 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  12. ISSUE: line 201 character 66: ['id'] is better written in dot notation. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  13. ISSUE: line 201 character 73: Missing semicolon. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  14. ISSUE: line 225 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 12:07, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 144 character 85: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem [0])
  5. ISSUE: line 148 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem [1])
  6. ISSUE: line 152 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem [2])
  7. ISSUE: line 160 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  8. ISSUE: line 163 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  9. ISSUE: line 168 character 34: Bad assignment. - Evidence: ii++ = 1;
  10. ISSUE: line 168 character 35: Missing semicolon. - Evidence: ii++ = 1;
  11. ISSUE: line 173 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  12. ISSUE: line 175 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  13. ISSUE: line 201 character 66: ['id'] is better written in dot notation. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  14. ISSUE: line 201 character 73: Missing semicolon. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  15. ISSUE: line 225 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 12:19, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 168 column 12: Invalid left-hand side in assignment

Your CommonsMaintenanceBot (talk) at 12:19, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 144 character 85: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem [0])
  5. ISSUE: line 148 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem [1])
  6. ISSUE: line 152 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem [2])
  7. ISSUE: line 160 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  8. ISSUE: line 163 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  9. ISSUE: line 173 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  10. ISSUE: line 175 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  11. ISSUE: line 201 character 66: ['id'] is better written in dot notation. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  12. ISSUE: line 201 character 73: Missing semicolon. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  13. ISSUE: line 225 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])
  14. ISSUE: line 226 character 72: Missing semicolon. - Evidence: var osm_elem = osm_elem + Overpass_elem [i] + "|"
  15. ISSUE: line 233 character 48: 'osm_elem' used out of scope. - Evidence: console.log("osm_elem =" + osm_elem );

Your CommonsMaintenanceBot (talk) at 12:38, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 84 character 41: Missing semicolon. - Evidence: waitForElement()
  2. ISSUE: line 122 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  3. ISSUE: line 133 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  4. ISSUE: line 145 character 85: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem [0])
  5. ISSUE: line 149 character 85: Missing semicolon. - Evidence: console.log("Overpass_elem [id] = " + Overpass_elem [1])
  6. ISSUE: line 153 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lat] = " + Overpass_elem [2])
  7. ISSUE: line 157 character 86: Missing semicolon. - Evidence: console.log("Overpass_elem [lon] = " + Overpass_elem [3])
  8. ISSUE: line 165 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  9. ISSUE: line 168 character 39: 'value' is already defined. - Evidence: var value = tagso[key];
  10. ISSUE: line 178 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  11. ISSUE: line 180 character 39: 'value' is already defined. - Evidence: var value = OverpassObject[key];
  12. ISSUE: line 206 character 66: ['id'] is better written in dot notation. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  13. ISSUE: line 206 character 73: Missing semicolon. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem["id"])
  14. ISSUE: line 228 character 39: Missing semicolon. - Evidence: var osm_elem = ""
  15. ISSUE: line 231 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 14:20, 12 February 2019 (UTC).[reply]


Code issues in User:Spratek11/common.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 1 column 18: Unexpected token :

Your CommonsMaintenanceBot (talk) at 12:37, 13 February 2019 (UTC).[reply]


Code issues in User:Spratek11/OSM info.js[edit]

Hi Spratek11, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Spratek11/OSM info.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 3 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 95 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in OverpassObject) {
  2. ISSUE: line 106 character 26: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in module){
  3. ISSUE: line 132 character 22: Creating global 'for' variable. Should be 'for (var key ...'. - Evidence: for( key in tagso) {
  4. ISSUE: line 151 character 66: ['id'] is better written in dot notation. - Evidence: console.log("Editace_Overpass_elem[id] " + Overpass_elem['id']);
  5. ISSUE: line 175 character 78: Missing semicolon. - Evidence: console.log("Var_Overpass_elem = " + Overpass_elem [i])

Your CommonsMaintenanceBot (talk) at 14:00, 13 February 2019 (UTC).[reply]

Retrieved from "https://commons.wikimedia.org/w/index.php?title=User_talk:Spratek11&oldid=338879820"