Skip to content

Migrate Documentation from Sphinx to MkDocs#2289

Merged
arkid15r merged 88 commits intovacanza:devfrom
Roshan-1024:sphinx-to-mkdocs
Mar 26, 2025
Merged

Migrate Documentation from Sphinx to MkDocs#2289
arkid15r merged 88 commits intovacanza:devfrom
Roshan-1024:sphinx-to-mkdocs

Conversation

@Roshan-1024
Copy link
Copy Markdown
Contributor

@Roshan-1024 Roshan-1024 commented Feb 12, 2025

Proposed change

This Draft PR migrates the documentation from Sphinx to MkDocs for simplicity and maintainability.

Changes so far:

  • Removed Sphinx-based docs/ folder.
  • Converted .rst files (CONTRIBUTING.rst, README.rst, RELEASE.rst) to Markdown (.md).
  • Added initial MkDocs setup (mkdocs.yml).
  • Cleaned up documentation formatting and added tips/warnings.
  • Updated Makefile to align with MkDocs.
  • Fixed Tables in README.md
  • Added feature: open external links in new tab with noopener noreferrer
  • Updated # Version to ## Version in Changelog.md
  • Added permalinks
  • Added site_description, site_author, site_name in mkdocs.yml
  • Added feature: show root heading
  • Converted all docstrings of countries, financial, holiday_base, utils, mixins files manually to Google-style
  • Removed the previous, next buttons under the toc
  • Added scripts to generate the nav for mkdocs-literate-nav to list all the countries and financial files
  • Removed deprecated functions and those starting with underscores
  • Included the documentation for undocumented members as well
  • Changed documentation member order to source for consistency

Type of change

  • New country/market holidays support (thank you!)
  • Supported country/market holidays update (calendar discrepancy fix, localization)
  • Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
  • Dependency update (version deprecation/pin/upgrade)
  • Bugfix (non-breaking change which fixes an issue)
  • Breaking change (a code change causing existing functionality to break)
  • New feature (new holidays functionality in general)

Checklist

@KJhellico
Copy link
Copy Markdown
Collaborator

@Roshan-1024, use merge instead of rebase next time, please.

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (1a81d99) to head (151809c).
Report is 1 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff            @@
##               dev     #2289   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          204       204           
  Lines        12853     12853           
  Branches      1817      1817           
=========================================
  Hits         12853     12853           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Roshan-1024
Copy link
Copy Markdown
Contributor Author

okay

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 17

🔭 Outside diff range comments (1)
pyproject.toml (1)

40-40: 🛠️ Refactor suggestion

Update documentation URL

The Documentation URL still points to ReadTheDocs with Sphinx. This should be updated to reflect the new MkDocs location.

-Documentation = "https://holidays.readthedocs.io/en/latest/"
+Documentation = "https://vacanza.github.io/holidays/" # or the appropriate MkDocs URL
♻️ Duplicate comments (3)
holidays/countries/timor_leste.py (1)

32-32: 🧹 Nitpick (assertive)

Remove trailing whitespace on blank line.

There is trailing whitespace on line 32 which should be removed to maintain clean code.

-    
+
docs/js/custom.js (2)

1-119: 🧹 Nitpick (assertive)

Consider adding section comments for better organization.

The JavaScript file handles multiple distinct functionalities. Adding clear section comments would improve maintainability.

document.addEventListener("DOMContentLoaded", () => {

+   // SECTION: External Links Handling
    // Opens external links in a new tab with security attributes
    document.querySelectorAll("a[href]").forEach(link => {
        if (link.hostname !== window.location.hostname) {
            link.setAttribute("target", "_blank");
            link.setAttribute("rel", "noopener noreferrer");
        }
    });

+   // SECTION: File Name Styling
    // Style File Name in the Webpage
    document.querySelectorAll(".doc.doc-object.doc-module").forEach(module => {
        // ... existing code
    });

+   // SECTION: Class Name Handling
    // Append "class" Before Class Names
    document.querySelectorAll(".doc.doc-object.doc-class").forEach(classElem => {
        // ... existing code
    });

+   // SECTION: Class Headers Styling
    // Style Class Headers
    document.querySelectorAll(".doc.doc-object.doc-class").forEach(classElem => {
        // ... existing code
    });

+   // SECTION: Class Contents Styling
    // Style Class Contents
    document.querySelectorAll(".doc.doc-object.doc-class").forEach(classElem => {
        // ... existing code
    });

+   // SECTION: Function Headers Styling
    // Style Function Headers
    document.querySelectorAll(".doc.doc-object.doc-function").forEach(funcElem => {
        // ... existing code
    });
});

28-64: 🧹 Nitpick (assertive)

Consider refactoring repetitive styling code.

The class headers styling section contains repetitive style application logic that could be extracted into a helper function for better maintainability.

+ // Utility function for applying styles
+ function applyStyles(element, styles) {
+     if (!element) return;
+     Object.assign(element.style, styles);
+ }

  // Style Class Headers
  document.querySelectorAll(".doc.doc-object.doc-class").forEach(classElem => {
      const codeElem = classElem.querySelector("h3 code");
      if (!codeElem) return;

      // Style "class" keyword
      const classKeyword = codeElem.querySelector(".class");
-     if (classKeyword) classKeyword.style.color = "#2980b9";
+     if (classKeyword) applyStyles(classKeyword, { color: "#2980b9" });
      
      // Style parameters inside class definition
      ["n", "o", "p", "kc"].forEach(cls => {
          codeElem.querySelectorAll(`.${cls}`).forEach((elem, index) => {
              if (cls === "n" && index === 0) return; // Skip first occurrence (class name)
-             elem.style.color = "#2980b9";
+             applyStyles(elem, { color: "#2980b9" });
          });
      });

      // Ensure class name is black
      const firstParam = codeElem.querySelector(".p");
      if (firstParam) {
          const firstN = codeElem.querySelector(".n");
-         if (firstN) firstN.style.color = "#000";
+         if (firstN) applyStyles(firstN, { color: "#000" });
      } else {
-         codeElem.style.color = "#000";
+         applyStyles(codeElem, { color: "#000" });
      }

      // Set background and border styles for class headers
      const h3Elem = classElem.querySelector("h3");
-     if (h3Elem) {
-         h3Elem.style.borderTop = "3px solid #6ab0de";
-         h3Elem.style.background = "#e7f2fa";
-         h3Elem.style.width = "fit-content";
-         h3Elem.style.paddingRight = "3px";
-     }
+     applyStyles(h3Elem, {
+         borderTop: "3px solid #6ab0de",
+         background: "#e7f2fa",
+         width: "fit-content",
+         paddingRight: "3px"
+     });
-     codeElem.style.background = "#e7f2fa";
-     codeElem.style.border = "none";
+     applyStyles(codeElem, {
+         background: "#e7f2fa",
+         border: "none"
+     });
  });
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 45b6dbc and a8a10b5.

📒 Files selected for processing (174)
  • .pre-commit-config.yaml (0 hunks)
  • CHANGES.md (80 hunks)
  • Makefile (1 hunks)
  • docs/js/custom.js (1 hunks)
  • holidays/countries/afghanistan.py (2 hunks)
  • holidays/countries/albania.py (2 hunks)
  • holidays/countries/algeria.py (2 hunks)
  • holidays/countries/american_samoa.py (1 hunks)
  • holidays/countries/andorra.py (1 hunks)
  • holidays/countries/angola.py (1 hunks)
  • holidays/countries/argentina.py (1 hunks)
  • holidays/countries/armenia.py (1 hunks)
  • holidays/countries/aruba.py (1 hunks)
  • holidays/countries/australia.py (1 hunks)
  • holidays/countries/austria.py (1 hunks)
  • holidays/countries/azerbaijan.py (3 hunks)
  • holidays/countries/bahamas.py (1 hunks)
  • holidays/countries/bahrain.py (2 hunks)
  • holidays/countries/bangladesh.py (1 hunks)
  • holidays/countries/barbados.py (1 hunks)
  • holidays/countries/belarus.py (2 hunks)
  • holidays/countries/belgium.py (1 hunks)
  • holidays/countries/belize.py (1 hunks)
  • holidays/countries/bolivia.py (1 hunks)
  • holidays/countries/bosnia_and_herzegovina.py (2 hunks)
  • holidays/countries/botswana.py (1 hunks)
  • holidays/countries/brazil.py (1 hunks)
  • holidays/countries/brunei.py (2 hunks)
  • holidays/countries/bulgaria.py (1 hunks)
  • holidays/countries/burkina_faso.py (2 hunks)
  • holidays/countries/burundi.py (2 hunks)
  • holidays/countries/cambodia.py (1 hunks)
  • holidays/countries/cameroon.py (2 hunks)
  • holidays/countries/canada.py (1 hunks)
  • holidays/countries/chad.py (2 hunks)
  • holidays/countries/chile.py (1 hunks)
  • holidays/countries/china.py (1 hunks)
  • holidays/countries/colombia.py (1 hunks)
  • holidays/countries/congo.py (1 hunks)
  • holidays/countries/costa_rica.py (1 hunks)
  • holidays/countries/croatia.py (1 hunks)
  • holidays/countries/cuba.py (1 hunks)
  • holidays/countries/curacao.py (1 hunks)
  • holidays/countries/cyprus.py (1 hunks)
  • holidays/countries/czechia.py (1 hunks)
  • holidays/countries/denmark.py (1 hunks)
  • holidays/countries/djibouti.py (2 hunks)
  • holidays/countries/dominica.py (2 hunks)
  • holidays/countries/dominican_republic.py (1 hunks)
  • holidays/countries/ecuador.py (1 hunks)
  • holidays/countries/egypt.py (2 hunks)
  • holidays/countries/el_salvador.py (1 hunks)
  • holidays/countries/estonia.py (1 hunks)
  • holidays/countries/eswatini.py (1 hunks)
  • holidays/countries/ethiopia.py (2 hunks)
  • holidays/countries/finland.py (1 hunks)
  • holidays/countries/france.py (1 hunks)
  • holidays/countries/gabon.py (2 hunks)
  • holidays/countries/georgia.py (2 hunks)
  • holidays/countries/germany.py (2 hunks)
  • holidays/countries/ghana.py (2 hunks)
  • holidays/countries/greece.py (1 hunks)
  • holidays/countries/greenland.py (1 hunks)
  • holidays/countries/guam.py (1 hunks)
  • holidays/countries/guatemala.py (1 hunks)
  • holidays/countries/guernsey.py (2 hunks)
  • holidays/countries/haiti.py (1 hunks)
  • holidays/countries/honduras.py (2 hunks)
  • holidays/countries/hongkong.py (1 hunks)
  • holidays/countries/hungary.py (2 hunks)
  • holidays/countries/iceland.py (1 hunks)
  • holidays/countries/india.py (2 hunks)
  • holidays/countries/indonesia.py (3 hunks)
  • holidays/countries/iran.py (2 hunks)
  • holidays/countries/ireland.py (1 hunks)
  • holidays/countries/isle_of_man.py (1 hunks)
  • holidays/countries/israel.py (1 hunks)
  • holidays/countries/italy.py (1 hunks)
  • holidays/countries/jamaica.py (1 hunks)
  • holidays/countries/japan.py (1 hunks)
  • holidays/countries/jersey.py (2 hunks)
  • holidays/countries/jordan.py (2 hunks)
  • holidays/countries/kazakhstan.py (3 hunks)
  • holidays/countries/kenya.py (3 hunks)
  • holidays/countries/kuwait.py (2 hunks)
  • holidays/countries/kyrgyzstan.py (1 hunks)
  • holidays/countries/laos.py (1 hunks)
  • holidays/countries/latvia.py (1 hunks)
  • holidays/countries/lesotho.py (1 hunks)
  • holidays/countries/liechtenstein.py (1 hunks)
  • holidays/countries/lithuania.py (1 hunks)
  • holidays/countries/luxembourg.py (1 hunks)
  • holidays/countries/macau.py (2 hunks)
  • holidays/countries/madagascar.py (1 hunks)
  • holidays/countries/malawi.py (1 hunks)
  • holidays/countries/malaysia.py (2 hunks)
  • holidays/countries/maldives.py (1 hunks)
  • holidays/countries/malta.py (1 hunks)
  • holidays/countries/marshall_islands.py (1 hunks)
  • holidays/countries/mauritania.py (1 hunks)
  • holidays/countries/mexico.py (1 hunks)
  • holidays/countries/moldova.py (1 hunks)
  • holidays/countries/monaco.py (1 hunks)
  • holidays/countries/montenegro.py (2 hunks)
  • holidays/countries/morocco.py (2 hunks)
  • holidays/countries/mozambique.py (1 hunks)
  • holidays/countries/namibia.py (1 hunks)
  • holidays/countries/netherlands.py (1 hunks)
  • holidays/countries/new_zealand.py (1 hunks)
  • holidays/countries/nicaragua.py (1 hunks)
  • holidays/countries/nigeria.py (2 hunks)
  • holidays/countries/north_macedonia.py (1 hunks)
  • holidays/countries/northern_mariana_islands.py (1 hunks)
  • holidays/countries/norway.py (1 hunks)
  • holidays/countries/pakistan.py (1 hunks)
  • holidays/countries/palau.py (2 hunks)
  • holidays/countries/panama.py (1 hunks)
  • holidays/countries/papua_new_guinea.py (2 hunks)
  • holidays/countries/paraguay.py (1 hunks)
  • holidays/countries/peru.py (1 hunks)
  • holidays/countries/philippines.py (2 hunks)
  • holidays/countries/poland.py (1 hunks)
  • holidays/countries/portugal.py (1 hunks)
  • holidays/countries/puerto_rico.py (1 hunks)
  • holidays/countries/romania.py (1 hunks)
  • holidays/countries/russia.py (1 hunks)
  • holidays/countries/saint_kitts_and_nevis.py (2 hunks)
  • holidays/countries/saint_lucia.py (1 hunks)
  • holidays/countries/samoa.py (1 hunks)
  • holidays/countries/san_marino.py (1 hunks)
  • holidays/countries/saudi_arabia.py (2 hunks)
  • holidays/countries/serbia.py (1 hunks)
  • holidays/countries/seychelles.py (2 hunks)
  • holidays/countries/singapore.py (3 hunks)
  • holidays/countries/slovakia.py (1 hunks)
  • holidays/countries/slovenia.py (1 hunks)
  • holidays/countries/south_africa.py (1 hunks)
  • holidays/countries/south_korea.py (2 hunks)
  • holidays/countries/spain.py (2 hunks)
  • holidays/countries/sri_lanka.py (3 hunks)
  • holidays/countries/sweden.py (1 hunks)
  • holidays/countries/switzerland.py (1 hunks)
  • holidays/countries/taiwan.py (2 hunks)
  • holidays/countries/tanzania.py (2 hunks)
  • holidays/countries/thailand.py (2 hunks)
  • holidays/countries/timor_leste.py (2 hunks)
  • holidays/countries/tonga.py (2 hunks)
  • holidays/countries/tunisia.py (1 hunks)
  • holidays/countries/turkey.py (2 hunks)
  • holidays/countries/tuvalu.py (1 hunks)
  • holidays/countries/ukraine.py (2 hunks)
  • holidays/countries/united_arab_emirates.py (3 hunks)
  • holidays/countries/united_kingdom.py (1 hunks)
  • holidays/countries/united_states.py (1 hunks)
  • holidays/countries/united_states_minor_outlying_islands.py (1 hunks)
  • holidays/countries/united_states_virgin_islands.py (1 hunks)
  • holidays/countries/uruguay.py (1 hunks)
  • holidays/countries/uzbekistan.py (2 hunks)
  • holidays/countries/vanuatu.py (1 hunks)
  • holidays/countries/vatican_city.py (1 hunks)
  • holidays/countries/venezuela.py (1 hunks)
  • holidays/countries/vietnam.py (2 hunks)
  • holidays/countries/zambia.py (1 hunks)
  • holidays/countries/zimbabwe.py (1 hunks)
  • holidays/holiday_base.py (18 hunks)
  • holidays/mixins.py (1 hunks)
  • holidays/utils.py (7 hunks)
  • mkdocs.yml (1 hunks)
  • pyproject.toml (2 hunks)
  • requirements/docs.txt (1 hunks)
  • scripts/docs/gen_changelog.py (1 hunks)
  • scripts/docs/gen_copyright.py (1 hunks)
  • scripts/docs/gen_ref_pages.py (1 hunks)
  • scripts/docs/gen_summary.py (1 hunks)
💤 Files with no reviewable changes (1)
  • .pre-commit-config.yaml
🧰 Additional context used
🧬 Code Definitions (4)
scripts/docs/gen_copyright.py (3)
scripts/docs/gen_changelog.py (1)
  • main (20-28)
scripts/docs/gen_ref_pages.py (1)
  • main (20-33)
scripts/docs/gen_summary.py (1)
  • main (20-44)
scripts/docs/gen_ref_pages.py (3)
scripts/docs/gen_changelog.py (1)
  • main (20-28)
scripts/docs/gen_copyright.py (1)
  • main (20-34)
scripts/docs/gen_summary.py (1)
  • main (20-44)
holidays/utils.py (1)
holidays/registry.py (3)
  • EntityLoader (203-297)
  • get_country_codes (270-276)
  • get_financial_codes (279-285)
scripts/docs/gen_summary.py (3)
scripts/docs/gen_changelog.py (1)
  • main (20-28)
scripts/docs/gen_copyright.py (1)
  • main (20-34)
scripts/docs/gen_ref_pages.py (1)
  • main (20-33)
🪛 markdownlint-cli2 (0.17.2)
CHANGES.md

19-19: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


32-32: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


52-52: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


76-76: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


87-87: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


108-108: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


120-120: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


135-135: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


155-155: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


180-180: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


195-195: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


220-220: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


235-235: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


264-264: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


280-280: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


298-298: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


305-305: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


317-317: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


331-331: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


345-345: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


357-357: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


372-372: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


386-386: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


402-402: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


415-415: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


429-429: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


439-439: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


458-458: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


483-483: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


498-498: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


511-511: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


527-527: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


547-547: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


570-570: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


589-589: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


601-601: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


623-623: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


635-635: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


654-654: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


693-693: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


713-713: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


737-737: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


743-743: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


778-778: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


817-817: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


838-838: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


861-861: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


889-889: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


921-921: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


939-939: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


971-971: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1021-1021: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1043-1043: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1084-1084: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1118-1118: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1133-1133: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1154-1154: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1175-1175: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1195-1195: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1228-1228: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1258-1258: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1273-1273: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1292-1292: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1307-1307: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1336-1336: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1353-1353: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1370-1370: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1390-1390: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1407-1407: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1424-1424: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1437-1437: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1452-1452: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1460-1460: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1469-1469: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1477-1477: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1484-1484: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1494-1494: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1502-1502: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1510-1510: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1526-1526: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1532-1532: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1542-1542: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1550-1550: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1562-1562: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1571-1571: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1578-1578: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1589-1589: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1595-1595: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1603-1603: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1611-1611: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)

🔇 Additional comments (334)
holidays/countries/luxembourg.py (1)

20-23: Good docstring improvement.

The updated format with a clear title and structured reference section makes the documentation more readable and consistent with standard Markdown practices. This aligns well with the migration from Sphinx to MkDocs.

holidays/countries/zimbabwe.py (1)

18-22: Good docstring reformatting.

The docstring has been well-structured with a clear separation between the description and references. The bullet point format with angle brackets for URLs follows Markdown best practices and improves readability. This change aligns with the overall documentation migration from Sphinx to MkDocs.

holidays/mixins.py (1)

17-17: Documentation format correctly updated to Markdown.

The reference to HongKong has been properly converted from reStructuredText format to Markdown link style. This change aligns well with the project's migration from Sphinx to MkDocs.

holidays/countries/poland.py (1)

21-26: Good documentation format conversion.

The changes from hyphenated list to Markdown bullet points are correct and consistent with the migration from Sphinx to MkDocs. This improves readability while maintaining all the reference information.

holidays/countries/lesotho.py (2)

19-20: Documentation enhancement looks good.

The addition of a clear summary line "Lesotho holidays." improves documentation clarity by immediately stating the purpose of this class.


22-24: Markdown formatting is well implemented.

The switch from hyphen bullets to asterisk bullets and the addition of angle brackets around URLs follows Markdown best practices. This change aligns well with the migration from Sphinx to MkDocs while improving link readability.

holidays/countries/malaysia.py (2)

66-83: Great work on the docstring improvement!

The updated docstring is much more structured and readable, with well-formatted Markdown links to references and clear explanations of holiday observance rules. This follows the project's move to MkDocs and Google-style documentation.


150-153: Docstring parameter format looks good.

The parameters section is now properly formatted using the Google-style "Args:" format, making it consistent with the project's new documentation standards.

holidays/countries/tuvalu.py (1)

24-35: Good docstring improvements

The changes to this docstring enhance readability in two key ways:

  1. Added a clear introductory statement "Tuvalu holidays." that immediately identifies the class purpose
  2. Reformatted references from hyphen-prefixed items to proper Markdown bullet points using asterisks

This formatting change aligns well with the migration from Sphinx to MkDocs and creates a more consistent documentation style across the codebase.

holidays/countries/south_africa.py (1)

19-25: Clean and improved documentation formatting.

The docstring has been updated to follow Markdown conventions with a clear title and properly formatted references section. This improves readability and aligns with the project's migration from Sphinx to MkDocs.

holidays/countries/malawi.py (1)

22-26: Documentation structure improved.

The changes to the docstring follow good Markdown practices with:

  • Clear title "Malawi holidays"
  • Dedicated "References" section
  • Properly formatted URL links using angle brackets for better rendering in Markdown

This improves readability and makes the documentation more consistent with Markdown standards.

holidays/countries/portugal.py (1)

24-34: Link formatting inconsistency in references section.

The references section has mixed link formatting styles that should be standardized for better readability:

  • Line 24 uses angle brackets <url>
  • Line 25 uses Markdown link syntax [text](url)
  • Lines 30-34 use angle brackets again

Choose one consistent style throughout the references section for better maintainability.

holidays/countries/northern_mariana_islands.py (1)

18-22: Good improvement to the docstring.

The updated docstring is clearer and follows better documentation practices. The title explicitly mentions "Northern Mariana Islands (the) holidays", making the purpose of the class immediately obvious. The URL formatting with angle brackets improves markdown rendering.

holidays/countries/peru.py (1)

20-24: Good docstring formatting improvement.

The updated docstring format uses proper Markdown styling with angle brackets for the URLs and asterisks for list items. This change aligns well with the migration from Sphinx to MkDocs and improves documentation readability.

This formatting will render better in MkDocs and is consistent with the broader documentation standardization effort mentioned in the PR objectives.

holidays/countries/kyrgyzstan.py (3)

19-19: Documentation formatting improvement.

The docstring has been simplified to a single line, which is cleaner and more consistent with Markdown-style documentation.


22-22: URL formatting updated to standard Markdown.

The reference link has been properly updated to use angle brackets, which is the correct Markdown syntax for URLs.


29-32: Docstring converted to Google-style format.

The parameter documentation has been successfully converted from Sphinx-style (:param) to Google-style (Args:), making it more consistent with the project's new documentation standards. The formatting is clear and well-structured.

holidays/countries/namibia.py (1)

19-24: Docstring formatting looks good.

The reformatting of the Namibia class docstring follows good Markdown practices with:

  • Clear title at the top
  • Dedicated "References" section
  • Properly formatted URL links in angle brackets
  • Consistent bullet point style

This change aligns well with the MkDocs migration goals and improves readability while maintaining all the original reference information.

holidays/countries/nicaragua.py (2)

20-20: Good addition of a concise class description.

Adding "Nicaragua holidays." as the introductory line provides an immediate clear description of the class purpose. This is a straightforward improvement that aligns with documentation best practices.


23-25: Format standardization looks good.

Converting reference bullet points from hyphens to asterisks follows standard Markdown formatting. This change is consistent with the migration from Sphinx to MkDocs and improves documentation readability across the project.

holidays/countries/vatican_city.py (3)

20-21: Documentation clarity improvement

Added clear and concise class description "Vatican City holidays." This improves documentation readability and makes the purpose of the class immediately obvious to users.


23-30: References section reformatted to standard Markdown

The references section has been properly converted from reStructuredText to Markdown format, using bullet points with asterisks and angle brackets for URLs. This follows standard Markdown practices and aligns with the MkDocs migration.


32-37: Cross-checked with section reformatted consistently

The "Cross-checked With" section has been correctly formatted following the same Markdown conventions as the References section. This maintains documentation consistency across the file.

holidays/countries/paraguay.py (2)

22-23: Documentation introduction adds clarity.

Adding "Paraguay holidays." as an introductory phrase to the docstring improves clarity right from the start. This addition aligns well with the migration from Sphinx to MkDocs and establishes consistency with other country class docstrings.


25-31: References section formatting improved for Markdown.

The reformatting of references from hyphen bullet points to asterisk bullet points properly aligns with Markdown syntax standards. This change is essential for the documentation migration from reStructuredText to Markdown and ensures proper rendering in MkDocs.

holidays/countries/slovenia.py (2)

22-23: Improved descriptive clarity in class docstring.

Adding "Slovenia holidays." makes the purpose of this class immediately obvious to readers. This is a solid improvement to the documentation.


25-28: Good conversion to Markdown format for references.

The change from hyphenated lists to Markdown-style asterisks with angle-bracketed URLs is appropriate for MkDocs and improves readability. This format will render properly in the new documentation system while maintaining clear source readability.

holidays/countries/sri_lanka.py (4)

52-60: Nicely formatted references section in SriLanka class.

The changes in this section convert the list formatting from RST-style hyphens to Markdown-style asterisks for bulleted lists. The addition of angle brackets around URLs improves readability and ensures they will render properly as clickable links in MkDocs.


62-76: Good conversion of the Cross-Checked With section.

The formatting changes from RST to Markdown are consistently applied here, maintaining the same structure and information while ensuring compatibility with MkDocs.


93-96: Args section properly converted to Markdown format.

The parameter documentation has been correctly updated to use Markdown formatting, which will render well in MkDocs documentation.


376-395: References section in SriLankaStaticHolidays class successfully converted.

The formatting changes here mirror those in the SriLanka class, ensuring consistency across the codebase. The conversion from RST to Markdown is well-executed, preserving all the reference links while updating the formatting style.

holidays/countries/zambia.py (1)

19-25: Documentation formatting improvement looks good.

The updated docstring format enhances readability by clearly separating the title from references and using proper Markdown bullet point notation for the URLs. This change aligns well with the migration from Sphinx to MkDocs and creates a consistent documentation style across country modules.

holidays/countries/laos.py (4)

23-39: Good conversion to Markdown format for references section

The documentation now uses proper Markdown formatting with bullet points and formatted links, which improves readability significantly. The change from hyphens to asterisks for bullet points and the use of Markdown-style hyperlinks make the references section much cleaner and more consistent.


38-38: Nice use of MkDocs-specific note formatting

The addition of the !!! note syntax leverages MkDocs features for better visual presentation of important information. This makes the note about weekend holidays more prominent and easier to spot.


42-46: Clean reformatting of the decree section

The section about the Decree on Holidays has been nicely reformatted while maintaining all the important information. Line 46 effectively explains the historical context of in-lieu holidays.


49-52: Improved formatting for limitations section

The limitations section is now properly indented and formatted, making it easier to read the constraints on the Laotian holiday calculations. The consistent indentation helps distinguish between the main points and their explanations.

holidays/countries/maldives.py (3)

19-20: Documentation improvement looks good.

The addition of "Maldives holidays." at the beginning of the class docstring provides a clear and concise description of what this class represents. This change improves the immediate understanding for users.


22-24: References formatting enhances readability.

The transition from hyphen-based list to angle bracket format for URLs follows Markdown best practices and aligns well with the MkDocs migration. This format will render properly in both GitHub and MkDocs documentation.


32-35: Parameter documentation style improvement.

The conversion from :param style to Google-style Args: format with proper indentation enhances readability and maintains consistency with the documentation standards being adopted. This change aligns perfectly with the PR's goal of standardizing docstrings.

holidays/countries/moldova.py (1)

22-26: Good improvement to documentation structure.

The docstring has been nicely reformatted with a clear title and properly organized references section. The use of bullet points with angle brackets for URLs follows good Markdown practices and improves readability.

While the PR objectives mention converting to Google-style docstrings, this simple documentation structure works well for this class since it doesn't have complex parameters or return values to document.

holidays/countries/latvia.py (1)

21-26: Good job transforming the docstring to Markdown format.

This follows the clear pattern used across other country modules with the introduction "Latvia holidays." followed by a "References:" section with proper Markdown-style links. The formatting with bullet points improves readability and maintainability.

holidays/countries/pakistan.py (2)

20-21: Class docstring improves documentation clarity.

Good addition of the concise class docstring. This enhances code documentation and makes the purpose of the class immediately clear to developers.


27-30: Parameter documentation format updated successfully.

The parameter documentation has been properly reformatted from the Sphinx-style :param format to the Google-style Args: format. This change is consistent with the PR objective of migrating documentation styles and improves readability.

holidays/countries/macau.py (2)

37-61: Documentation formatting looks good in the Macau class.

The docstring for the Macau class has been properly formatted using Markdown-style bullet points for all references, which aligns with the overall documentation migration from Sphinx to MkDocs.


411-414: Markdown Link Formatting in Special Public and Government Holidays

The static holidays section still uses angle brackets for the special public and government holiday references. For consistency with the rest of the document and the Cross-Checking section below (lines 417-418), consider switching to the standard Markdown link format (e.g., [Link Text](URL)).

holidays/countries/samoa.py (2)

18-19: Good addition of a clear class summary.

The addition of "Samoa holidays." provides an immediate, clear description of what this class represents. This improves documentation clarity and aligns with good docstring practices.


21-24: Documentation formatting improvement.

The references have been properly reformatted with angle brackets around URLs, which follows Markdown link syntax that will render correctly in MkDocs. The switch from hyphens to asterisks for bullet points maintains consistent formatting across the codebase.

holidays/countries/united_states_minor_outlying_islands.py (1)

17-22: Enhanced and Clear Docstring for HolidaysUM Class
The updated multi-line docstring now clearly explains that this class handles holidays for the United States Minor Outlying Islands and includes a handy reference URL in angle brackets. This improves overall readability and consistency with the enhanced documentation style. For future consistency, consider verifying that similar updates in other country-specific classes follow the same structure.

holidays/countries/mexico.py (1)

20-27: Documentation formatting looks good.

The changes to the documentation follow proper Markdown formatting standards:

  • Clear class description added
  • References section now uses consistent bullet formatting with asterisks
  • URLs properly enclosed in angle brackets for better rendering in Markdown

These changes align well with the migration from Sphinx to MkDocs mentioned in the PR objectives.

holidays/countries/uzbekistan.py (3)

23-24: Good addition of concise class title

The title "Uzbekistan holidays." is clear and immediately tells users what this class represents. This follows the same pattern used in other country classes and improves consistency.


26-28: References properly formatted in Markdown style

The references section has been successfully converted from RST to Markdown format. The use of asterisk bullets and proper Markdown link syntax enhances readability while maintaining all reference information.


44-47: Parameter documentation converted to Google-style format

Good conversion from :param syntax to Google-style Args: format. The parameter description is properly indented and clear, making it compatible with mkdocstrings. This aligns with the PR objective of standardizing documentation.

holidays/countries/nigeria.py (2)

26-29: Good improvement to documentation structure.

The addition of a dedicated "References" section with the URL in angle brackets enhances readability and follows better documentation practices. This change aligns with standardization efforts across country classes.


38-41: Clean conversion to Google-style docstring format.

The transition from Sphinx-style parameter documentation to Google-style with the "Args:" heading improves consistency with the project's new documentation approach. The parameter description is well-structured with proper indentation.

holidays/countries/united_arab_emirates.py (3)

38-58: Good job on the docstring improvements

The conversion to Google-style docstrings with proper Markdown formatting looks clean. The references section with bullet points and properly formatted URLs in angle brackets significantly improves readability and will render well in MkDocs.


70-75: Docstring parameter style properly updated

Nice work converting the parameter documentation from Sphinx-style (:param) to Google-style (Args:). This change maintains consistency across the codebase and follows best practices for MkDocs documentation.


201-216: Well-formatted static holidays docstring

The docstring improvements for UnitedArabEmiratesStaticHolidays follow the same good practices as the main class. The nested bullet points and consistent URL formatting enhance readability and structure.

holidays/countries/timor_leste.py (4)

30-31: Clean docstring formatting.

The docstring follows good Markdown formatting practices with proper spacing.


33-40: Improved references section with better formatting.

The references section has been updated with proper Markdown bullet points using asterisks instead of hyphens. Additionally, new references for 2024 and 2025 have been added, making the documentation more complete and up-to-date.


43-43: Updated limitation information.

The limitation statement has been correctly updated to reflect that exact Islamic holidays dates are now available for 2011-2025 instead of just 2011-2023, which aligns with the data in TimorLesteIslamicHolidays class (lines 194-228).


57-60: Improved parameter documentation with Google-style format.

The parameter documentation has been properly converted from Sphinx-style (:param) to Google-style (Args:) format, which is more readable and aligns with the PR's goal of standardizing documentation.

holidays/countries/montenegro.py (2)

37-42: Documentation format improved with Markdown links

The docstring has been effectively reformatted with a clear title and properly formatted Markdown links for references. This change enhances readability and aligns with the migration from Sphinx to MkDocs.


59-62: Docstring converted to Google-style format

The parameter documentation has been properly converted to Google-style format with an "Args:" section. This structured approach improves readability and makes the documentation more consistent with modern Python documentation standards.

holidays/countries/isle_of_man.py (1)

21-21: Enhanced Class Docstring for Clarity

The updated docstring "Isle Of Man holidays." is concise and clearly communicates the purpose of the class. This change improves the readability and aligns well with the overall documentation migration from Sphinx to MkDocs. Keep up the good work!

holidays/countries/spain.py (4)

29-29: Docstring heading is more concise.

Good simplification of the class docstring header. Moving the specific date information to the end of the docstring maintains the information while making the initial description more focused.


32-48: Well-formatted references with Markdown links.

Nice improvement in formatting the references section using Markdown-style asterisk lists and hyperlinks. This change:

  • Makes the documentation more interactive
  • Improves readability
  • Follows Markdown best practices
  • Maintains all the essential reference information

The hyperlinks will be particularly helpful in the generated MkDocs documentation, allowing users to navigate directly to the official sources.


50-50: Updated date range coverage to 2025.

Good update to extend the date range of officially verified holidays from 2023 to 2025. This matches the new references added above and keeps the documentation accurate and up-to-date.


82-85: Google-style parameter documentation.

The parameter documentation now follows Google-style formatting, which is more readable with MkDocs and conforms to modern Python documentation standards. The indentation and structure make the parameter description clear and easy to follow.

holidays/countries/philippines.py (3)

36-38: Documentation format looks good.

The docstring has been simplified to a single line description, which is clear and consistent with the Markdown migration.


39-52: References section properly reformatted to Markdown.

The references section has been effectively converted to Markdown format with:

  • Proper bullet points using asterisks
  • Well-formatted links using the standard Markdown [text](url) syntax
  • Consistent styling throughout the list

This change improves readability and aligns with the MkDocs migration.


65-68: Parameter documentation follows Google style correctly.

The parameter documentation has been updated to use the Google-style "Args" section format, which improves readability and is consistent with the project's docstring standardization goals.

holidays/countries/singapore.py (2)

44-61: Well-formatted Markdown documentation provides better clarity

The docstring now uses proper Markdown formatting with organized sections for references and limitations, making the documentation more readable. The links are properly formatted with Markdown syntax which works well with MkDocs.


69-75: Good adoption of Google-style docstrings

The Args section follows Google docstring conventions with proper parameter descriptions and formatting. This makes it easy to understand the parameter purpose and improves the documentation quality.

holidays/countries/new_zealand.py (1)

27-28: Good addition of class docstring.

The new docstring "New Zealand holidays." clearly describes the purpose of the class. This aligns with the migration from Sphinx to MkDocs and improves code documentation.

holidays/countries/austria.py (1)

21-22: Appropriate docstring added.

Adding "Austria holidays." as a class docstring provides immediate context to developers. This change is consistent with documentation improvements in other country classes.

holidays/countries/estonia.py (1)

20-21: Clear and consistent docstring added.

The new docstring "Estonia holidays." follows the same pattern as other country classes, maintaining consistency across the codebase.

holidays/countries/netherlands.py (1)

23-28: Successfully converted bullet points to Markdown format.

The References section has been updated from RST-style hyphen bullets to Markdown-style asterisk bullets. This change is consistent with the migration from Sphinx to MkDocs.

holidays/countries/slovakia.py (1)

22-27: Documentation formatting looks good.

The changes to use bullet points with angle brackets for URLs improve readability and consistency with Markdown format, which works well with MkDocs.

holidays/countries/curacao.py (1)

23-27: Documentation structure improved.

The addition of a clear "Curaçao holidays" title and structured "References" section with properly formatted links enhances readability and follows Markdown best practices.

holidays/countries/aruba.py (1)

22-31: Documentation formatting is well structured.

The changes properly organize the docstring with a clear title and references section. The links are correctly formatted with angle brackets for Markdown compatibility.

holidays/countries/russia.py (1)

22-26: Documentation format consistently applied.

The standardized format with a clear title and properly formatted reference links maintains consistency with the other country classes in the codebase.

holidays/countries/canada.py (1)

31-43: Documentation format update looks good!

The docstring format update to Markdown style is well-done. Adding "Canada holidays." as a title and converting the reference links to bullet points with asterisks improves readability and follows Markdown conventions.

holidays/countries/switzerland.py (1)

22-27: Clean Markdown-style documentation update.

The conversion from reStructuredText to Markdown format is properly implemented. The addition of "Switzerland holidays." as a title and the bullet-point formatting with asterisks follows good Markdown practices.

holidays/countries/botswana.py (1)

24-30: Well-structured documentation formatting.

The docstring has been nicely restructured with a clear title "Botswana holidays.", explicit "References:" section, and properly formatted bullet points. This aligns well with Markdown conventions and improves documentation clarity.

holidays/countries/costa_rica.py (1)

26-36: Consistent documentation format improvement.

The docstring update follows the same pattern as other country classes with the addition of a clear title and bullet-point formatting for references. The consistent approach across files helps maintain a uniform documentation style throughout the project.

holidays/countries/andorra.py (1)

18-22: Documentation formatting updated to Markdown style

The docstring has been reformatted from reStructuredText to Markdown syntax, with bullet points using asterisks and links enclosed in angle brackets. This change improves readability and aligns with the migration from Sphinx to MkDocs.

holidays/countries/finland.py (1)

22-32: Documentation formatting standardized to Markdown

The reference links have been updated to follow Markdown conventions, with bullet points and properly formatted links. This change supports the MkDocs migration while maintaining all the original reference information.

holidays/countries/iran.py (2)

36-42: References section updated to Markdown format

The reference links have been converted to Markdown syntax with bullet points, making them compatible with MkDocs while preserving all original reference information.


56-59: Constructor documentation updated to Google style

The parameter documentation has been converted from reStructuredText's :param style to Google style with Args: sections. This standardization makes the docstrings more readable and consistent with modern Python documentation practices.

holidays/countries/malta.py (1)

20-28: References section enhanced with descriptive Markdown links

The references section has been significantly improved by:

  1. Adding a clear "References:" header
  2. Using consistent bullet point formatting
  3. Converting plain URLs to descriptive Markdown links where appropriate

This formatting greatly enhances readability while maintaining all the source information, supporting the migration to MkDocs.

holidays/countries/hongkong.py (1)

54-67: Good update to Markdown-style formatting

The docstring has been reformatted from hyphenated lists to bullet points using Markdown syntax (asterisks), which aligns well with the move from Sphinx to MkDocs. This format will render properly in MkDocs documentation.

holidays/countries/brazil.py (1)

23-30: Documentation format improved for MkDocs compatibility

The references section has been updated to use angle brackets around URLs and asterisks for bullet points, following proper Markdown formatting. This is consistent with the documentation migration from Sphinx to MkDocs.

holidays/countries/czechia.py (1)

20-26: Documentation standardized for MkDocs

The docstring formatting has been improved to use Markdown-style bullet points with asterisks and angle brackets for URLs. This change enhances readability and maintains consistency with the MkDocs migration.

holidays/countries/marshall_islands.py (1)

21-25: Docstring properly structured for MkDocs

The documentation has been reorganized with a clear title and properly formatted references section using Markdown bullet points and angle brackets for URLs. This enhancement improves readability and aligns with the project's migration to MkDocs.

holidays/countries/taiwan.py (2)

48-69: Documentation formatting looks good.

The switch to Markdown-style links with angle brackets and asterisk bullet points aligns well with the MkDocs migration. The formatting is consistent and improves readability.


267-297: Great consistency in documentation formatting.

The TaiwanStaticHolidays class documentation follows the same formatting pattern as the Taiwan class, maintaining consistency throughout the file.

holidays/countries/madagascar.py (1)

19-26: Documentation formatting correctly updated.

The docstring has been properly formatted with Markdown-style links and consistent bullet points. The addition of "Madagascar holidays." as the opening line follows the standard pattern being applied across all country classes.

holidays/countries/bangladesh.py (1)

19-24: Documentation style correctly updated.

The conversion to Markdown format with angle-bracketed links and asterisk bullet points has been implemented consistently. The "Bangladesh holidays." opening follows the standard pattern adopted across country classes.

holidays/countries/liechtenstein.py (1)

21-26: Documentation format properly converted.

The docstring has been successfully converted to Markdown format with the consistent pattern of starting with "Liechtenstein holidays." and using angle brackets for links. This maintains consistency with the documentation style being implemented across the codebase.

holidays/countries/kuwait.py (3)

21-22: Improved class introduction.

The updated docstring now clearly identifies "Kuwait holidays." as the purpose of the class, which improves readability and matches the pattern used across other country classes.


24-26: Good reference formatting.

The references have been updated to use angle brackets around URLs and asterisks for list items, which aligns with Markdown formatting standards and improves readability when rendered in MkDocs.


37-40: Good migration to Google-style docstring format.

The parameter documentation has been updated from Sphinx-style :param to Google-style Args:, which improves readability and consistency with the overall documentation migration.

holidays/countries/saint_lucia.py (2)

20-20: Clear class introduction.

The updated docstring now explicitly states "Saint Lucia holidays." which improves clarity about the class purpose.


23-27: Consistent reference formatting.

References are now formatted with angle brackets around URLs and asterisks for list items, maintaining consistency with other country modules and improving MkDocs rendering.

holidays/countries/seychelles.py (2)

21-30: Well-structured docstring with mixed reference formats.

The references section has been properly formatted with angle brackets and asterisks. I noticed you're using a combination of plain URLs and descriptive links with Markdown syntax on lines 27-29, which is a good practice for providing context about each reference.


121-133: Consistent formatting for static holidays class.

The docstring for SeychellesStaticHolidays follows the same formatting pattern as the main class, maintaining consistency throughout the file.

holidays/countries/romania.py (1)

21-26: Documentation follows consistent pattern.

The docstring formatting with "Romania holidays." introduction and properly formatted references aligns with the changes made across other country modules.

holidays/countries/greece.py (1)

26-30: Consistent documentation format enhances readability.

The docstring formatting has been updated to follow Markdown standards, which aligns with the migration from Sphinx to MkDocs. The clear structure with a descriptive title line and properly formatted reference links improves documentation consistency.

holidays/countries/bosnia_and_herzegovina.py (3)

45-52: Well-structured documentation with proper formatting.

The docstring has been nicely organized with a clear title and properly formatted reference links using Markdown bullet points. This format is consistent with the MkDocs migration.


54-57: Enhanced Observed Holiday Rules List

Converting the observed holiday rules into a clear bullet-point list greatly enhances the documentation's clarity. Consider a minor grammatical tweak, e.g., using "if a holiday falls on Sunday" for improved readability, though this is just a nitpick.


80-84: Properly formatted parameter documentation.

The Args section follows Google-style docstring formatting, which is well-structured and clear. This provides better readability for developers using the library.

holidays/countries/bulgaria.py (1)

23-30: Improved documentation structure and consistency.

The docstring has been well-organized with a clear title and comprehensive references section using consistent Markdown formatting. This standardization makes the documentation more accessible and maintainable, aligning perfectly with the MkDocs migration.

holidays/countries/vanuatu.py (1)

19-25: Documentation formatting enhances readability.

The docstring has been formatted with a clear title and properly structured references using Markdown bullet points. This consistent approach across the codebase improves maintainability and user experience.

holidays/countries/belize.py (1)

23-29: Documentation format looks good!

The conversion to Markdown-style formatting with a clear title "Belize holidays." and proper bulleted references with angle brackets improves readability and consistency. This aligns well with the migration from Sphinx to MkDocs.

holidays/countries/monaco.py (1)

21-25: Documentation format is consistent and well-structured.

The updated docstring format with "Monaco holidays." as the title and properly formatted references using bullet points with angle brackets follows good Markdown conventions. This is consistent with other country modules and supports the MkDocs migration.

holidays/countries/jordan.py (2)

21-25: Documentation format improvements look good.

The addition of "Jordan holidays." as the title and conversion of references to bullet points with angle brackets enhances readability and follows proper Markdown syntax.


36-40: Parameter documentation format is improved.

The switch from :param style to Google-style Args: with proper indentation makes the documentation more readable and maintainable. This format allows for clearer multiline descriptions and better visual separation between the parameter name and its description.

holidays/countries/cameroon.py (2)

27-33: Documentation format is consistent with other modules.

The addition of "Cameroon holidays." as the title and converting references to properly formatted bullet points follows the established pattern across the codebase. This consistency is important for maintainability.


42-46: Parameter documentation follows Google style properly.

The reformatting to Google-style documentation with Args: and proper indentation improves readability. This approach provides a clear structure for parameter documentation and allows for well-formatted multiline descriptions.

holidays/countries/uruguay.py (1)

27-36: Documentation format improved with better structure

The docstring now includes a clear title "Uruguay holidays." and standardized bullet-point references, making the documentation more readable and consistent with Markdown conventions.

holidays/countries/el_salvador.py (1)

20-25: Improved Reference Presentation

The documentation now mixes a Markdown-styled link (for the Labor Code) with angle-bracket enclosed URLs. While this enhances clarity, consider unifying the style across all reference entries for ultimate consistency.

holidays/countries/india.py (2)

31-39: Great clarity with the new URL formatting!

The bullet list with angle-bracketed URLs is much clearer and consistent. Consider adding a brief introductory summary (e.g., "Reference URLs:" or similar) at the start of the docstring to provide extra context and align with Google-style docstring conventions.


153-156: Args section format follows Google style docstring conventions

The parameter documentation has been updated to use the Google style with an "Args:" section and proper indentation, which is more consistent with the documentation migration effort.

holidays/countries/cyprus.py (2)

22-22: Documentation formatting improved for class description

The class description has been standardized to a clear, concise format.


25-26: Documentation references formatted consistently

The reference links have been properly formatted with asterisks and angle brackets, improving readability.

holidays/countries/dominican_republic.py (1)

25-29: Documentation structure improved

The class docstring has been reformatted with a clear title "Dominican Republic holidays" and a well-structured References section. The updated format with angle brackets improves readability.

holidays/countries/turkey.py (3)

23-23: Documentation title standardized

The class description has been standardized to a clear format.


25-29: References section formatting improved

The references section has been reformatted consistently with asterisks for bullet points and proper link formatting. The mix of angle brackets and Markdown-style links provides clear distinction between different types of references.


43-46: Parameter documentation style updated to Google format

The parameter documentation has been updated from using :param to the Google-style Args: format with improved indentation and description clarity. This aligns with the PR objective of converting docstrings to Google-style.

holidays/countries/united_kingdom.py (2)

27-27: Documentation title standardized

The class description has been standardized to "United Kingdom holidays" format, improving consistency.


30-33: References formatting standardized

The references have been reformatted with asterisks for bullet points and angle brackets for URLs, improving readability and consistency across the documentation.

holidays/countries/chad.py (2)

27-31: Docstring formatting looks good

The updated docstring follows the proper Markdown formatting with angle brackets for URLs and maintains consistency with other files in the project. This aligns well with the MkDocs migration.


41-44: Good conversion to Google-style docstrings

The parameter documentation has been properly converted from RST-style to Google-style with the "Args:" section. The formatting with the indentation for the description improves readability.

holidays/countries/denmark.py (1)

21-26: Consistent Markdown formatting for references

The references section now properly uses Markdown formatting with angle brackets for URLs. This follows the same pattern as other country modules and will render correctly in MkDocs.

holidays/countries/ghana.py (2)

22-26: Clean Markdown formatting for documentation

The docstring has been properly formatted with a clear title and structured references section. The angle brackets around URLs follow Markdown best practices.


37-40: Well-structured Google-style parameter documentation

The parameter documentation follows Google-style conventions with the "Args:" section and proper indentation for the description. The line breaks improve readability.

holidays/countries/croatia.py (1)

20-26: Improved docstring structure

The docstring has been reformatted with a clear title and well-organized references section. The Markdown formatting with angle brackets for URLs will display properly in MkDocs.

CHANGES.md (1)

1-1618: Clean Markdown heading conversion looks great!

The conversion from RST-style version headers with equals signs to Markdown headers using the hash symbol is well executed and consistent throughout the entire changelog. This change aligns perfectly with the migration from Sphinx to MkDocs.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

19-19: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


32-32: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


52-52: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


76-76: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


87-87: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


108-108: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


120-120: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


135-135: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


155-155: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


180-180: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


195-195: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


220-220: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


235-235: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


264-264: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


280-280: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


298-298: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


305-305: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


317-317: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


331-331: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


345-345: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


357-357: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


372-372: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


386-386: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


402-402: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


415-415: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


429-429: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


439-439: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


458-458: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


483-483: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


498-498: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


511-511: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


527-527: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


547-547: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


570-570: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


589-589: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


601-601: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


623-623: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


635-635: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


654-654: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


693-693: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


713-713: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


737-737: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


743-743: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


778-778: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


817-817: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


838-838: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


861-861: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


889-889: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


921-921: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


939-939: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


971-971: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1021-1021: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1043-1043: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1084-1084: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1118-1118: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1133-1133: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1154-1154: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1175-1175: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1195-1195: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1228-1228: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1258-1258: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1273-1273: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1292-1292: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1307-1307: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1336-1336: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1353-1353: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1370-1370: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1390-1390: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1407-1407: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1424-1424: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1437-1437: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1452-1452: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1460-1460: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1469-1469: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1477-1477: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1484-1484: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1494-1494: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1502-1502: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1510-1510: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1526-1526: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1532-1532: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1542-1542: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1550-1550: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1562-1562: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1571-1571: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1578-1578: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1589-1589: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1595-1595: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1603-1603: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)


1611-1611: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)

holidays/countries/bolivia.py (1)

25-36: Well-formatted Markdown references!

The conversion of references to a proper Markdown bullet list with formatted links improves readability while maintaining all the original information. The use of angle brackets for URLs and square bracket + parentheses syntax for titled links follows Markdown best practices.

holidays/countries/barbados.py (1)

24-33: Clean docstring formatting conversion!

The references section has been properly converted to Markdown format with bullet points and correctly formatted links. This change maintains all the original information while improving the clarity and readability of the documentation.

holidays/countries/china.py (1)

22-64: Excellent documentation formatting with consistent style!

The references, "Checked With", and "Limitations" sections have been cleanly converted to Markdown formatting with proper bullet points. The consistent use of angle brackets for URLs and the proper indentation of multi-line bullet points demonstrate careful attention to documentation quality.

holidays/countries/angola.py (1)

28-42: Documentation formatting improvements look good!

The changes from hyphen-based bullet points to asterisks and the addition of properly formatted Markdown links enhance readability. The clear "Angola holidays." heading also provides immediate context about the class purpose.

holidays/countries/ecuador.py (1)

27-31: Documentation formatting improvements look good!

The changes align well with the MkDocs migration by standardizing on asterisk-based bullet points and proper Markdown link formatting. The consistent "Ecuador holidays." heading matches the pattern applied to other country classes.

holidays/countries/france.py (1)

20-24: Documentation structure improved

The reorganization of the docstring with a concise title and properly formatted References section with asterisk bullet points is a good improvement. This makes the documentation more consistent with other country classes.

holidays/countries/guatemala.py (1)

22-30: Documentation formatting improvements look good!

The changes to standardize on asterisk bullet points and proper Markdown link formatting in both the References and Moving holidays sections enhance the readability and consistency of the documentation.

holidays/countries/germany.py (3)

22-22: Docstring content simplified appropriately

The class description has been simplified from "Official holidays for Germany in its current form" to "Germany holidays." This concise approach aligns with the documentation standardization effort.


26-29: Minor formatting improvement in paragraph

The formatting changes in this paragraph maintain the same content while improving readability.


246-248: References formatting updated to Markdown

The references section has been properly updated from reStructuredText format to Markdown, using angle brackets for URLs which is the correct syntax for MkDocs.

holidays/countries/tunisia.py (1)

30-34: Parameter documentation converted to Google-style

The parameter documentation has been successfully converted to Google-style format using the "Args:" section header. This improves readability and matches the project's new documentation standards.

holidays/countries/albania.py (3)

30-32: Class description added

Added a concise class description "Albania holidays." which follows the new documentation standard.


33-35: References formatted to Markdown

The references have been properly formatted using Markdown syntax. URLs are in angle brackets and named links use the text format, which is correct for MkDocs.


52-56: Parameter documentation converted to Google-style

The parameter documentation has been properly converted from Sphinx-style :param to Google-style using the "Args:" section, improving readability and consistency.

holidays/countries/congo.py (3)

20-21: Class description added

Added a concise class description "Congo holidays." which aligns with the new documentation standard.


23-24: References formatted to Markdown

The references have been properly converted to use Markdown-style links with the text format, which is appropriate for MkDocs.


27-27: URL format updated to Markdown syntax

The URL has been properly updated to use angle brackets, which is the correct Markdown syntax for URLs in MkDocs.

holidays/countries/bahamas.py (1)

26-39: Consistent format improvements in class docstring

The docstring formatting has been standardized to follow Markdown conventions with asterisk bullet points and properly formatted links. This improves readability and aligns with the project's move to MkDocs.

holidays/countries/burkina_faso.py (2)

20-24: Improved docstring format with better introduction

The addition of a clear introductory line and proper Markdown formatting for the reference links enhances documentation clarity.


34-38: Clean conversion to Google-style parameter documentation

The parameter documentation has been properly converted from RST-style to Google-style format, improving readability and consistency.

holidays/countries/afghanistan.py (2)

36-42: Consistent Markdown formatting with improved structure

The docstring now follows a clear structure with a descriptive introduction and properly formatted reference links using Markdown conventions.


55-59: Well-structured parameter documentation

The parameter documentation has been properly converted to Google-style format with clear separation between the parameter name and its description.

holidays/countries/papua_new_guinea.py (2)

21-36: Comprehensive docstring improvements with consistent formatting

The docstring now includes a clear introduction and properly formatted references and checked sources using Markdown conventions. The mix of link styles (Markdown links and angle bracket links) is handled consistently.


135-149: Enhanced static holidays class documentation

The documentation for PapuaNewGuineaStaticHolidays has been improved with better formatting and more descriptive notes. The consistent use of Markdown formatting enhances readability.

holidays/countries/georgia.py (2)

23-23: Documentation formatting improved for Georgia class docstring

The docstring format has been standardized to use consistent spacing and Markdown-friendly syntax for the class description.

The reference links have been updated to use asterisks and angle brackets, which follows Markdown best practices and improves rendering in MkDocs.

Also applies to: 26-27


106-106: Reference link format standardized in GeorgiaStaticHolidays class

The reference link has been updated to use angle brackets, maintaining consistency with other reference links throughout the codebase and ensuring proper rendering in MkDocs documentation.

holidays/countries/mauritania.py (2)

19-20: Documentation formatting improved for class description and references

The docstring has been standardized to include "Mauritania holidays." as a clear first line with proper spacing. The reference links now use the Markdown-friendly format with asterisks and angle brackets, which improves rendering in MkDocs.

Also applies to: 22-23


31-34: Parameter documentation converted to Google-style format

The parameter documentation has been updated from RST-style (:param:) to Google-style docstring format using Args: with improved formatting and line breaks. This change enhances readability and maintains consistency with the documentation migration to MkDocs.

holidays/countries/iceland.py (1)

21-22: Documentation formatting improved for Iceland class

The docstring format has been standardized to include "Iceland holidays." as a clear first line with proper spacing. The reference links now follow Markdown best practices using asterisks and angle brackets, which improves rendering in MkDocs.

Also applies to: 24-25

holidays/countries/bahrain.py (2)

22-22: Documentation formatting standardized for Bahrain class

The docstring has been updated to include "Bahrain holidays." as a clear first line. The reference links now use Markdown-friendly format with asterisks and angle brackets, which improves documentation consistency across the project.

Also applies to: 25-26


38-41: Parameter documentation converted to Google-style format

The parameter documentation has been updated from RST-style to Google-style docstring format with improved structure using Args: and better line breaks. This change improves readability and aligns with the project-wide documentation migration to MkDocs.

holidays/countries/armenia.py (1)

21-26: Documentation formatting improvements look good

The docstring has been reformatted to use Markdown-style links with angle brackets, which aligns perfectly with the migration from Sphinx to MkDocs. The references section is now more readable with consistent formatting.

holidays/countries/serbia.py (1)

21-24: Well-formatted docstring conversion

The changes to the docstring format look good. Converting from RST-style references to Markdown format with angle brackets makes the documentation more consistent with MkDocs standards.

holidays/countries/eswatini.py (1)

21-25: Properly structured docstring formatting

Good work on reformatting the docstring to use a clear "References:" section with proper Markdown-style links. This is consistent with the documentation migration goals and improves readability.

holidays/countries/belarus.py (2)

23-36: Documentation formatting consistent with MkDocs standards

The docstring formatting changes for both the main references and cross-checked sections look good. The angle-bracketed links follow Markdown best practices and will display correctly in MkDocs.


149-152: Consistent formatting in BelarusStaticHolidays class

The docstring formatting in the BelarusStaticHolidays class follows the same consistent pattern as the main class. Good attention to detail in maintaining formatting consistency across all docstrings.

holidays/countries/chile.py (1)

30-58: Documentation formatting looks good.

The references have been properly converted to Markdown format using bullet points and angle brackets for URLs. This standardization helps with the migration to MkDocs.

holidays/countries/lithuania.py (1)

20-24: Documentation improvements are consistent.

The docstring title and URL formatting changes align with the project's move to Markdown-based documentation with MkDocs.

holidays/countries/saint_kitts_and_nevis.py (1)

22-27: Documentation standardization is thorough.

Both class docstrings have been correctly updated to the new Markdown format with proper titles, spacing, and URL formatting. This consistency is important for MkDocs documentation generation.

Also applies to: 126-140

holidays/countries/venezuela.py (1)

20-30: Excellent documentation enhancement.

The Venezuela class docstring has been significantly improved with a clear title and extensive, well-formatted references. The additional historical links provide valuable context while maintaining the new Markdown format standard.

holidays/countries/indonesia.py (3)

44-51: Well-formatted Markdown docstring.

The conversion from RST to Markdown format with properly formatted URLs in angle brackets and bullet points improves readability both in code and in rendered documentation.


68-71: Appropriate conversion to Google-style docstrings.

The change from RST-style :param to Google-style Args: format aligns with the project's move to MkDocs, which works well with this documentation style.


592-610: Consistent reference formatting.

Good job maintaining consistency in the reference formatting across classes, with proper Markdown bullet points and angle-bracketed URLs.

holidays/countries/cambodia.py (2)

22-34: Well-structured documentation sections.

The docstring has been properly formatted with Markdown conventions. The References and Checked with sections use consistent bullet points with angle brackets around URLs, improving readability.


35-40: Clean limitations section formatting.

The limitations section has been converted to bullet points while preserving the original content, making it more readable in rendered Markdown.

holidays/countries/morocco.py (2)

20-25: Consistently formatted docstring.

The docstring has been converted to Markdown format with proper bullet points and angle brackets around URLs, maintaining the same pattern as other country modules.


35-39: Properly converted parameter documentation.

The change from RST-style parameter documentation to Google-style format improves consistency with the MkDocs documentation approach.

holidays/countries/saudi_arabia.py (2)

30-36: Clean docstring conversion to Markdown.

The docstring has been simplified and reformatted to use Markdown conventions with proper bullet points and angle brackets around URLs.


50-54: Consistent parameter documentation style.

The parameter documentation has been converted from RST-style to Google-style format, consistent with the approach used in other country modules.

holidays/countries/azerbaijan.py (3)

28-33: Improved reference formatting in docstring.

The docstring references are now properly formatted with Markdown-style links using asterisks and angle brackets, making them more readable and consistent with MkDocs standards.


50-53: Better parameter documentation structure.

Converting the parameter documentation to an "Args" section enhances readability and follows Google-style docstring conventions, which works well with mkdocstrings.


267-277: Consistent reference formatting throughout the file.

The references in AzerbaijanStaticHolidays class are now properly formatted with Markdown-style links, matching the formatting used elsewhere in the codebase.

holidays/countries/burundi.py (2)

18-25: Improved docstring clarity and formatting.

The docstring now uses a more direct "Burundi holidays" title and properly formatted reference links with Markdown syntax. The note about holidays falling on Sunday is preserved while improving readability.


34-37: Better parameter documentation structure.

Converting to Google-style "Args" section improves consistency and readability while maintaining the original meaning.

holidays/countries/belgium.py (1)

21-27: Standardized docstring format.

The docstring now follows the consistent pattern of "Country holidays" and properly formatted reference links using Markdown syntax with angle brackets.

holidays/countries/australia.py (1)

29-49: Improved reference formatting in docstring.

The references section now uses consistent Markdown-style formatting with asterisk bullet points and angle brackets for URLs. This enhances readability and aligns with the MkDocs documentation standard being implemented across the project.

holidays/countries/argentina.py (2)

30-95: Documentation improvement: Better formatted references section.

The references section has been reformatted to use Markdown styling with bold headers and properly formatted links. This improves readability and aligns with the migration from Sphinx to MkDocs documentation.


106-113: Documentation improvement: Consistent formatting of Movable Holidays Laws section.

The Movable Holidays Laws section has been reformatted to match the style used in the references section, creating a consistent documentation style throughout the file.

holidays/countries/haiti.py (1)

24-26: Documentation improvement: Updated references format.

The references section has been reformatted to use Markdown-style links with angle brackets. This improves readability and is consistent with the project's migration to MkDocs.

holidays/countries/vietnam.py (2)

48-52: Documentation improvement: Reformatted references section.

The references section has been updated to use Markdown formatting with properly formatted links. This is aligned with the project's documentation migration effort.


153-156: Documentation improvement: Consistent formatting in VietnamStaticHolidays class.

The references section in the VietnamStaticHolidays class has been consistently reformatted to match the style used in the main Vietnam class.

holidays/countries/palau.py (3)

20-20: Documentation improvement: Added descriptive header.

Added "Palau holidays." to the docstring, providing a clear description of the class purpose. This makes the documentation more informative.


23-26: Documentation improvement: Reformatted references section.

The references section has been updated to use Markdown-style formatting with angle brackets for links, improving readability and consistency with other files.


109-115: Documentation improvement: Restructured PalauStaticHolidays docstring.

Added a descriptive header and reformatted the references section in the PalauStaticHolidays class to match the style used throughout the project.

holidays/countries/ethiopia.py (3)

24-27: Consistent bullet point formatting looks good

The bullet point formatting has been updated from hyphens to asterisks, aligning with Markdown best practices and the overall migration to MkDocs.


38-49: Great documentation improvement

The expanded docstring for _is_leap_year method provides much clearer explanation of how Ethiopian leap years relate to Gregorian leap years. The added context about the calendar shift and its impact on holidays will be helpful for maintainers.


55-58: Proper Google-style docstring format

The parameter documentation has been updated to use the Google-style "Args:" section instead of the previous colon format, consistent with the documentation migration goals.

holidays/countries/panama.py (1)

22-30: Reference links formatting improvement

The references section has been updated to use proper Markdown formatting with asterisk bullet points and better link formatting. This improves readability and is consistent with the MkDocs migration.

holidays/countries/tanzania.py (4)

30-42: References section formatting looks good

The references section has been reformatted to use asterisks for bullet points and proper Markdown link syntax, improving readability in MkDocs output.


44-50: Checked With section formatting improvement

The "Checked With" section has been updated with consistent Markdown formatting using asterisks for bullet points.


52-57: Limitations section bullet consistency

The limitations section now uses consistent asterisk bullet points for both main and nested items, addressing the previous review comment about bullet point consistency.


71-74: Google-style Args section implemented correctly

The parameter documentation has been updated to follow Google-style docstring format with the "Args:" section, consistent with the project's documentation migration.

holidays/countries/ireland.py (2)

19-20: Added descriptive class docstring

The docstring now starts with "Ireland holidays." which provides immediate context about the class purpose, improving documentation clarity.


22-23: References formatting updated for Markdown

The reference links now use asterisk bullet points instead of hyphens, making them consistent with Markdown best practices and the MkDocs migration.

holidays/countries/cuba.py (1)

20-48: Documentation formatting improved for clarity.

The docstring has been effectively restructured with proper Markdown formatting, making it more readable and organized. The use of bullet points and hyperlinks enhances the documentation's usability.

holidays/countries/colombia.py (1)

20-33: Well-structured references with proper Markdown syntax.

The reformatting of references to use bullet points and proper Markdown link syntax improves readability. The historical calendar links are now more clearly organized.

holidays/countries/jersey.py (2)

28-39: Clear documentation title and consistent reference formatting.

The addition of a descriptive title and the reformatting of references using consistent Markdown syntax enhances documentation clarity.


162-180: Standardized documentation for JerseyStaticHolidays class.

The docstring now follows the same standardized format as other classes, with a clear title and properly formatted references using angle brackets.

holidays/countries/italy.py (1)

19-23: Consistent Markdown formatting applied.

The docstring now follows the standardized format with a clear title and properly formatted references using both angle brackets and Markdown link syntax.

holidays/countries/brunei.py (2)

57-104: Documentation format looks good

The standardization to markdown-style links and Google-style docstrings enhances readability and aligns well with MkDocs. References are well-formatted with consistent styling.


121-124: Parameter documentation format is consistent

The transition to Google-style docstrings with the "Args:" section matches the project's new documentation standards and works well with mkdocstrings.

requirements/docs.txt (1)

3-8: Confirm MkDocs dependencies selection

The dependencies align with the migration to MkDocs, but differ slightly from KJhellico's previous suggestions. Could you confirm:

  1. Why mkdocs is explicitly included when previously suggested it could be omitted?
  2. Why zipp is pinned to a specific version (3.21.0) rather than using >=3.19.1?

These changes may be intentional based on further testing, but verification would be helpful.

holidays/countries/kazakhstan.py (3)

32-39: Documentation format is consistent

The change to asterisk-based bullet points maintains consistency with other files in the project and improves readability in markdown format.


56-59: Google-style parameter documentation looks good

The "Args:" format aligns with the project's standardization to Google-style docstrings.


174-226: Well-structured KazakhstanStaticHolidays documentation

Great improvement moving the substituted holidays references to the KazakhstanStaticHolidays class where they logically belong. The comprehensive reference list with nested bullets provides excellent context and maintainability.

holidays/countries/egypt.py (1)

33-36: Parameter documentation format looks good

The standardization to Google-style docstrings with the "Args:" section is consistent and works well with mkdocstrings.

holidays/countries/tonga.py (4)

27-36: Good update on the docstring formatting

The conversion to Markdown-style links with angle brackets improves readability and maintainability. The use of asterisks for bullet points is consistent with Markdown conventions.


39-45: Well-structured "Checked With" section

The reformatting of the "Checked With" section using Markdown-style links makes the references more visually distinct and easier to follow.


49-73: Improved readability of observance rules

The removal of leading dashes and better spacing in the observance rules text significantly improves readability while preserving all the original information.


206-212: Consistent formatting in TongaStaticHolidays class

The styling changes in the TongaStaticHolidays class docstring match the formatting improvements made to the main Tonga class, maintaining consistency throughout the file.

holidays/countries/hungary.py (2)

21-27: Good restructuring of docstring

The new format with a clear "Hungary holidays." title and dedicated "References" section improves the organization of the documentation while maintaining all essential information.


117-134: Well-formatted references in HungaryStaticHolidays

The conversion to Markdown-style links with years as link text provides a cleaner, more structured appearance that makes the references easier to scan and understand.

holidays/countries/guernsey.py (2)

26-35: Good docstring formatting update

The addition of a clear title "Guernsey holidays." and the consistent use of Markdown-style links for references improves readability and aligns with the project's new documentation style.


235-265: Comprehensive reference list reformatting

The extensive list of references in the GuernseyStaticHolidays class has been well-formatted using consistent Markdown-style links, making this previously dense section much more readable.

holidays/countries/jamaica.py (1)

23-28: Good consistent documentation style

The changes to the Jamaica class docstring follow the same pattern as other country classes, with a clear title and properly formatted references, contributing to a unified documentation style across the project.

holidays/countries/kenya.py (3)

36-42: Docstring improvement: Kenya class has better formatted documentation now

The addition of a clear class description and properly formatted Markdown links improves the documentation's readability. This change aligns well with the MkDocs migration objectives.


59-63: Nice conversion to Google-style docstrings

Converting parameters to use the Args format with proper indentation follows Google docstring conventions, making it more compatible with MkDocs documentation generation.


207-220: Improved documentation for KenyaStaticHolidays class

Adding a clear class description and converting references to proper Markdown format with angle brackets enhances readability and consistency with the rest of the codebase.

holidays/countries/algeria.py (2)

21-27: Better formatted class description and references

The addition of a clear class description and properly formatted references with Markdown links improves documentation readability. This change is consistent with the MkDocs migration.


37-41: Well-structured parameter documentation

Converting to Google-style docstrings with the Args format improves documentation consistency and readability, making it more compatible with mkdocstrings.

holidays/countries/gabon.py (2)

20-27: Consistent docstring formatting improvements

Adding a clear class description and properly formatting references with Markdown links enhances readability. The consistent approach across different country classes is commendable.


35-39: Google-style docstring conversion implemented well

Properly formatted Args section with appropriate indentation follows Google docstring conventions, which aligns with the overall documentation migration strategy.

holidays/countries/japan.py (1)

35-40: Enhanced docstring format for Japan class

Adding a concise class description and converting references to proper Markdown format with angle brackets improves documentation readability. The consistency with other country classes is excellent.

holidays/countries/israel.py (1)

31-35: Documentation format looks good now

The updated docstring references with angle brackets follow Markdown conventions, which aligns with the migration from Sphinx to MkDocs. This change makes the links properly render as clickable URLs in the generated documentation.

holidays/countries/norway.py (3)

21-32: Clean docstring transformation

The restructured docstring with References section and consistent formatting improves readability. The explanatory notes about Sundays as holidays are now better organized.


39-39: Type annotation added

Good addition of type annotation for include_sundays parameter, which improves code quality and provides better IDE support.


41-43: Args format looks good

Switching to Google-style docstring format with "Args:" section matches the documentation standardization mentioned in the PR objectives.

holidays/countries/djibouti.py (2)

21-22: Added missing class docstring

Good addition of the class docstring which was previously missing. This improves code documentation.


34-37: Parameter documentation standardized

The switch to Google-style docstring format with "Args:" section is consistent with the changes made in other files.

pyproject.toml (2)

5-5: README format updated

Changed README reference from RST to MD format, which aligns with the PR's objective of migrating from Sphinx to MkDocs.


45-45: Removed docs from exclude_dirs

Removed "docs" from the bandit exclude_dirs list, which makes sense since the Sphinx docs directory has been removed in favor of MkDocs.

holidays/countries/sweden.py (3)

21-36: Good improvement to documentation format

The documentation is now more readable with clearer section headers and properly formatted references.


42-42: Nice type hint addition

Adding the bool type hint to include_sundays parameter improves code clarity and IDE support.


44-46: Good parameter documentation format

Converting from :param to Google-style Args: format with indentation improves readability.

holidays/countries/dominica.py (3)

22-26: Documentation format is now consistent

Good job converting from hyphens to asterisks for bullet points and enclosing URLs in angle brackets.


28-31: References section is more readable now

The Cross-Checked section is more consistently formatted with descriptive labels for links.


110-116: Consistent formatting in static holidays class

The documentation in DominicaStaticHolidays class now follows the same formatting conventions as the main class.

holidays/countries/thailand.py (5)

48-88: References formatted consistently

Good job converting the large references section to use standardized Markdown formatting with angle brackets for URLs and asterisks for bullet points.


90-153: Well-organized sections with descriptive formatting

The sections for "Checked with", "In Lieus", and "Certain holidays references" are now more readable with proper Markdown formatting.


149-173: Improved readability with info and note blocks

Using !!! info "Info" and !!! note "Note" formatting enhances the visibility of important information in the documentation.


174-181: Limitations section is now consistently formatted

The limitations section now uses asterisks for bullet points, consistent with the rest of the documentation.


975-976: Fixed bullet point format in ThailandStaticHolidays

The reference now uses asterisk instead of hyphen for consistency with the rest of the documentation.

holidays/countries/ukraine.py (2)

25-30: Documentation is now cleaner and more readable

Good conversion to concise format with proper Markdown-style for references.


171-218: Consistent references formatting throughout

The extensive list of references for substituted and special holidays is now properly formatted with asterisks for bullet points and angle brackets for URLs.

holidays/countries/north_macedonia.py (2)

19-22: Excellent formatting of class documentation.

The new docstring structure with a clear title and properly formatted reference link is a significant improvement over the previous bare URL approach.


29-32: Good conversion to Google-style docstring format.

The parameter documentation has been properly converted from Sphinx-style (:param:) to Google-style (Args:), improving readability while maintaining the same information.

holidays/countries/honduras.py (2)

20-24: Well-structured class documentation with proper references.

The updated docstring now includes a clear title and properly formatted reference links with descriptive text. This is more informative and better organized than the previous format.


58-58: Simplified comment reference.

Converting the full URL to a concise reference to "Decree 78-2015" makes the code cleaner while maintaining the connection to the relevant legislation.

holidays/utils.py (15)

44-46: Good restructuring of function description.

The function description is now more clearly separated from the parameter documentation, improving readability.


47-80: Well-formatted parameter documentation.

The parameter documentation has been effectively converted from Sphinx-style (:param:) to Google-style (Args:), with proper indentation and clear separation between parameters. Each parameter description is now more readable with proper line breaks.


82-84: Added clear return value documentation.

The explicit Returns: section makes it immediately clear what the function returns, which is an improvement over the previous format.


93-98: Improved formatting of list items.

The bullet points for accepted date types are now properly formatted with Markdown asterisks, improving readability in MkDocs output.


111-158: Well-formatted code examples.

The code examples are now properly formatted with consistent indentation, making them more readable in both source code and generated documentation.


174-182: Improved code block formatting.

The code example is now properly wrapped in a Markdown code block with triple backticks and language specification, which will render better in MkDocs.


218-241: Consistent parameter documentation format.

The parameter documentation for financial_holidays() follows the same pattern as country_holidays(), ensuring consistency throughout the documentation.


251-252: Proper cross-reference formatting.

The reference to country_holidays() now uses a Markdown-style link format with proper function path, which will render as a clickable link in MkDocs.


274-275: Clear deprecation notice format.

The deprecation notice is now formatted with a Note: section, which will stand out better in the generated documentation.


288-295: Consistent documentation style across helper functions.

The helper function _list_localized_entities() follows the same documentation pattern as the main functions, ensuring consistency throughout the codebase.


314-321: Consistently formatted documentation for list functions.

The documentation for list_localized_countries() maintains the same style as other functions, with clear parameter and return sections.


331-337: Consistent parameter documentation format in financial functions.

The documentation for list_localized_financial() follows the same pattern as other functions, ensuring consistency throughout the API.


346-352: Uniform documentation style for internal functions.

Even internal helper functions like _list_supported_entities() have been updated to use the same documentation style, showing attention to detail in documentation consistency.


367-373: Maintain documentation pattern across related functions.

The documentation for list_supported_countries() follows the same pattern as the other list functions, ensuring a consistent API documentation experience.


383-389: Complete set of consistent documentation updates.

The final function list_supported_financial() has also been updated with the same documentation pattern, completing a thorough and consistent documentation update throughout the file.

holidays/holiday_base.py (27)

59-71: Improved class documentation with better formatting.

The main class docstring now uses proper Markdown formatting for better readability and follows a consistent style pattern seen across the codebase.


83-87: Enhanced reference formatting with Markdown links.

References to other functions are now properly formatted as Markdown links, which will render as clickable links in MkDocs documentation.


94-98: Consistently formatted list items.

The bullet point list of accepted date types uses Markdown asterisks for consistency with other documentation in the codebase.


112-115: Well-formatted code examples with clear comments.

The code examples are properly formatted with consistent indentation and include clear comments to indicate specific use cases.


129-131: Consistent code example formatting.

Additional code examples maintain the same formatting style, ensuring a consistent documentation experience.


140-141: Properly aligned code examples and output.

The example code and its expected output are properly aligned and consistently formatted.


145-158: Well-formatted multi-line code examples.

The longer code example that lists all 2020 holidays is properly formatted with consistent indentation, making it easier to read.


162-164: Consistent formatting of comparison examples.

The examples showing regional holiday differences are formatted consistently with other examples.


168-172: Improved formatting of list items with descriptions.

The bullet points explaining different ways to append holidays are well-formatted with proper indentation and consistent style.


175-183: Properly formatted code block with triple backticks.

The code example is now properly wrapped in a Markdown code block with triple backticks, which will render correctly in MkDocs.


186-187: Consistent reference formatting.

References to attributes like special_public_holidays now use backticks for code formatting, ensuring consistency.


207-208: Proper Markdown link format for class references.

The reference to HolidayBase class now uses a proper Markdown link format that will render as a clickable link in MkDocs.


269-303: Comprehensive parameter documentation in init method.

The documentation for the __init__ method parameters is thorough and well-formatted, clearly describing each parameter and its purpose.


404-418: Enhanced documentation for the contains method.

The __contains__ method now has comprehensive documentation that clearly explains its purpose, supported input types, and return value.


586-600: Improved technical documentation for keytransform method.

The documentation for the internal __keytransform__ method is now much clearer, with a comprehensive explanation of supported input types and return value.


747-751: Fixed missing return value documentation.

The get_subdivision_aliases() method now has proper return value documentation, addressing the issue mentioned in a previous review comment.


925-934: Complete documentation for append method.

The append() method now has proper documentation for both parameters and behavior, addressing the issue mentioned in a previous review comment about empty documentation.


942-963: Comprehensive get method documentation.

The get() method documentation now fully describes the accepted input types, parameters, and return value, addressing the issue mentioned in a previous review comment.


984-1010: Detailed parameter documentation for get_named method.

The documentation for the get_named() method thoroughly describes all parameters, including the lookup options and their specific behaviors.


1046-1062: Complete documentation for get_closest_holiday method.

The get_closest_holiday() method now has comprehensive documentation that explains both parameters and return value, addressing the issue mentioned in a previous review comment.


1084-1099: Clear parameter and return documentation for get_nth_working_day.

The documentation for the get_nth_working_day() method now properly describes both parameters and the return value, addressing the issue mentioned in a previous review comment.


1108-1123: Added return value documentation for get_working_days_count.

The get_working_days_count() method now has proper return value documentation, addressing the issue mentioned in a previous review comment.


1132-1140: Improved documentation for is_working_day method.

The is_working_day() method now has clear parameter and return value documentation, addressing the issue mentioned in a previous review comment.


1175-1191: Well-structured documentation for pop_named method.

The pop_named() method documentation clearly explains its purpose, parameters, return value, and potential exceptions.


1219-1233: Complete update method documentation.

The update() method now has thorough documentation for its parameters and behavior, addressing the issue mentioned in a previous review comment about empty documentation.


1247-1252: Improved HolidaySum class documentation.

The documentation for the HolidaySum class has been reformatted for better readability while maintaining the same information content.


1269-1295: Well-formatted documentation for HolidaySum init method.

The documentation for the HolidaySum.__init__() method includes clear parameter descriptions and a comprehensive example with expected output.

docs/js/custom.js (5)

1-10: Good implementation of external links handler.

The event listener properly identifies external links and sets them to open in new tabs with security attributes (rel="noopener noreferrer"), which is a good security practice.


11-19: File name styling implementation is clean and focused.

The module styling logic is well-scoped and clearly handles the file name appearance in the documentation.


20-27: Class name styling looks good.

The code effectively prepends "class" to class names using template literals, making the documentation more readable.


66-92: Class attribute styling logic works well.

The styling for class attributes and contents is appropriately implemented, with good separation of concerns between different style aspects.


94-119: Function header styling is implemented properly.

The code correctly applies styles to function headers, making the documentation more readable. The logic for differentiating between function names and parameters is clear.

Makefile (1)

32-33: Good simplification of documentation build process.

The change from sphinx-build to mkdocs build aligns with the PR objective of migrating from Sphinx to MkDocs. The simpler command indicates a more straightforward configuration process, which is a positive improvement.

holidays/countries/united_states_virgin_islands.py (1)

18-22: Improved docstring formatting.

The docstring has been reformatted to use a clearer style with better spacing and the URL is properly enclosed in angle brackets for Markdown compatibility. This change is consistent with the documentation standardization effort.

scripts/docs/gen_changelog.py (3)

1-12: Good inclusion of header documentation.

The script includes appropriate headers with author information and licensing details, maintaining consistency with other files in the codebase.


13-18: Import section is concise and appropriate.

The script imports only what's necessary: Path from pathlib for file operations and mkdocs_gen_files for generating MkDocs files.


31-32: Good execution guard pattern.

The script uses a proper execution guard to check if it's being run as a main module or via a run path, which is a good practice.

scripts/docs/gen_copyright.py (4)

1-12: Header looks good.

The file header clearly identifies the project, purpose, and licensing information.


13-14: Docstring accurately describes the purpose.

The docstring concisely explains what the script does.


15-18: Good import organization.

Imports are separated by type (standard library and third-party) with appropriate spacing.


37-38: Good script entry point.

The module uses a proper if statement to check if it's being run directly, including support for <run_path> which allows it to be executed by various tools.

scripts/docs/gen_ref_pages.py (4)

1-12: Header looks good.

The file header clearly identifies the project, purpose, and licensing information.


13-14: Docstring accurately describes the purpose.

The docstring concisely explains what the script does and where the generated files will be placed.


15-18: Good import organization.

Imports are separated by type (standard library and third-party) with appropriate spacing.


36-37: Good script entry point.

The module uses a proper if statement to check if it's being run directly, including support for <run_path> which allows it to be executed by various tools.

scripts/docs/gen_summary.py (4)

1-12: Header looks good.

The file header clearly identifies the project, purpose, and licensing information.


13-14: Docstring accurately describes the purpose.

The docstring concisely explains what the script generates and its purpose for navigation.


15-18: Good import organization.

Imports are separated by type (standard library and third-party) with appropriate spacing.


47-48: Good script entry point.

The module uses a proper if statement to check if it's being run directly, including support for <run_path> which allows it to be executed by various tools.

holidays/countries/guam.py (1)

17-22: Improved docstring format.

The comment has been correctly converted to a proper docstring with:

  1. A concise first line description
  2. An empty line separator
  3. Additional context about Guam's status
  4. Proper Markdown formatting for the URL

This aligns with the PR objective to convert to Google-style docstrings and improve documentation quality.

mkdocs.yml (2)

1-7: Site Metadata & Theme Configuration Look Good
The metadata section (site_description, site_author, site_name) is clearly defined and the theme is correctly set using the readthedocs style with syntax highlighting enabled. Nice and clean!


42-47: Extra Assets Configuration Is Consistent
The extra_css and extra_javascript sections are concise and use consistent indentation. This setup should efficiently bring in your custom styles and scripts without issues.

holidays/countries/american_samoa.py (1)

18-22: Refined Docstring for HolidaysAS Class
The updated docstring now uses the proper multi-line string format, adheres to Google style, and neatly includes the URL reference using angle brackets. This makes the class documentation clearer and more user-friendly.

Comment on lines +326 to 337
"""South Korea special holidays.

References:
- https://namu.wiki/w/임시공휴일 *
- https://namu.wiki/w/공휴일/대한민국 **
- https://namu.wiki/w/대체%20휴일%20제도
* <https://namu.wiki/w/임시공휴일> *
* <https://namu.wiki/w/공휴일/대한민국> **
* <https://namu.wiki/w/대체%20휴일%20제도>

(1) Election Dates featured here are the ones prior to the proper recodification to
1. Election Dates featured here are the ones prior to the proper recodification to
Article 34 of the Public Official Election Act(September 2006)
(2) Sabang Day (사방의 날) was technically in the Public Holidays Act itself, but since it was
2. Sabang Day (사방의 날) was technically in the Public Holidays Act itself, but since it was
only celebrated in 1960, this is being put here.
"""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Enhanced Docstring in SouthKoreaStaticHolidays Class

This docstring has been reformatted to adopt Markdown conventions, including a numbered list and the use of asterisks for bullet points. A quick nitpick: verify that the extra asterisks at the end of some reference lines (e.g., "*", "**") are intentional for styling purposes rather than accidental. Otherwise, the update looks good.

# Conflicts:
#	holidays/countries/philippines.py
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a8a10b5 and 7a5b36a.

📒 Files selected for processing (5)
  • holidays/countries/philippines.py (2 hunks)
  • holidays/financial/brasil_bolsa_balcao.py (1 hunks)
  • holidays/financial/european_central_bank.py (1 hunks)
  • holidays/financial/ice_futures_europe.py (1 hunks)
  • holidays/financial/ny_stock_exchange.py (2 hunks)
🔇 Additional comments (5)
holidays/financial/ice_futures_europe.py (1)

18-24: Docstring formatting properly converted to Markdown style

The references section has been updated to use Markdown-style URL formatting with angle brackets, which is consistent with the project's migration from Sphinx to MkDocs. The links remain intact and this change enhances documentation readability.

holidays/financial/european_central_bank.py (1)

19-25: Good call on standardizing the reference formatting.

The change from hyphens to asterisks for bullet points and adding angle brackets around URLs aligns perfectly with Markdown best practices. This improves readability while ensuring consistency with the MkDocs migration mentioned in the PR objectives.

holidays/countries/philippines.py (2)

36-54: Enhanced Class Docstring with Consistent Markdown Formatting

The updated docstring now offers a concise one-line description followed by a bullet-point list for references. This improves readability and aligns with the new documentation standards. Please double-check that all link texts are free of any extraneous formatting (e.g., stray backticks) to ensure uniformity across the project.


66-70: Improved init Docstring in Google Style

The constructor’s docstring has been revised to use a structured "Args:" section, which enhances clarity. This pattern will help maintain consistent documentation for future parameters.

holidays/financial/ny_stock_exchange.py (1)

152-157: Consistent formatting across docstrings.

The docstring for NewYorkStockExchangeStaticHolidays follows the same improved format as the main class, with proper URL formatting in angle brackets under the References section.

# Conflicts:
#	holidays/countries/philippines.py
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

♻️ Duplicate comments (1)
holidays/countries/philippines.py (1)

36-55: 🧹 Nitpick (assertive)

Docstring Formatting for Philippines Class

Great job updating the class docstring to a concise, single-line description and reformatting the references into a clear bullet-point list with Markdown-style links. One minor suggestion: the first reference still uses angle brackets around the URL; consider converting it to the same Markdown link format as the others for consistency. This update also neatly addresses previous concerns about extraneous backticks.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4bb17ca and 0977d6e.

📒 Files selected for processing (1)
  • holidays/countries/philippines.py (2 hunks)
⏰ Context from checks skipped due to timeout of 300000ms (1)
  • GitHub Check: Test build on windows-latest

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0977d6e and 1fa62c7.

📒 Files selected for processing (11)
  • holidays/countries/argentina.py (1 hunks)
  • holidays/countries/azerbaijan.py (3 hunks)
  • holidays/countries/belarus.py (2 hunks)
  • holidays/countries/cuba.py (1 hunks)
  • holidays/countries/dominica.py (2 hunks)
  • holidays/countries/georgia.py (2 hunks)
  • holidays/countries/germany.py (2 hunks)
  • holidays/countries/saint_kitts_and_nevis.py (2 hunks)
  • holidays/countries/seychelles.py (2 hunks)
  • holidays/countries/thailand.py (2 hunks)
  • holidays/utils.py (7 hunks)
🧰 Additional context used
🧬 Code Definitions (1)
holidays/utils.py (1)
holidays/registry.py (3)
  • EntityLoader (203-297)
  • get_country_codes (270-276)
  • get_financial_codes (279-285)
🔇 Additional comments (29)
holidays/countries/argentina.py (2)

26-63: Documentation formatting improved for references section

The references section has been well-reformatted using Markdown syntax, making it more readable and consistent with the MkDocs migration. The use of proper link formatting and hierarchical structure improves documentation clarity.


64-69: Movable Holidays Laws formatting enhanced for readability

The Movable Holidays Laws section has been reformatted with clear hierarchical structure and consistent formatting, making the information easier to scan and understand.

holidays/countries/cuba.py (1)

20-49: Well-structured and informative docstring conversion.

The updated docstring effectively organizes information with clear sections and properly formatted Markdown links. This is a solid improvement over the previous format and aligns well with the documentation migration objectives. The content preserves all the important historical context while making it more readable.

I particularly appreciate:

  • The organized References section with proper Markdown link formatting
  • The clear structuring of the holiday details with nested bullet points
  • The preservation of important policy information about holiday observance rules
holidays/countries/georgia.py (2)

23-28: Docstring format improved for better Markdown compatibility.

The changes to the Georgia class docstring properly align with Markdown standards, making the documentation more consistent with the migration from Sphinx to MkDocs. The use of angle brackets around URLs will make them render correctly as clickable links in Markdown output.


103-107: Docstring standardization for GeorgiaStaticHolidays looks good.

The updated format matches the Markdown standards applied to the rest of the codebase. Consistent formatting across all docstrings will improve the documentation readability in MkDocs.

holidays/countries/dominica.py (4)

19-20: Docstring formatting looks good.

The opening format for the Dominica class docstring follows clean Markdown standards, which aligns well with the MkDocs migration.


22-25: Reference formatting is correctly updated.

The references section has been properly converted to Markdown format with URLs enclosed in angle brackets, which improves readability and follows standard Markdown conventions.


28-31: Cross-check references properly formatted.

The "Cross-Checked With" section now uses a consistent format with both descriptive labels in square brackets followed by URLs in parentheses and direct URLs in angle brackets. This mixed approach is valid in Markdown and improves documentation clarity.


109-115: DominicaStaticHolidays references properly formatted.

The docstring for the DominicaStaticHolidays class has been correctly updated to use Markdown formatting for the references section, maintaining consistency with the rest of the file.

holidays/countries/seychelles.py (2)

21-28: Documentation formatting looks good

The references are now consistently formatted using Markdown-style angle brackets for URLs, with proper description for the Act link. This aligns well with the migration to MkDocs.


120-132: References section properly converted to Markdown

The links are correctly formatted with angle brackets for clean Markdown rendering. This consistency helps maintain a uniform documentation style across the project.

holidays/countries/saint_kitts_and_nevis.py (2)

22-31: Documentation improvement looks good.

The addition of a clear title and the reformatting of references with proper Markdown syntax (URLs in angle brackets) enhances readability and consistency. This aligns well with the migration from Sphinx to MkDocs.


125-141: Well-structured documentation update.

The docstring now includes a proper title and comprehensive references with consistent Markdown formatting. The extensive list of reference URLs provides valuable context for the special holidays implementation.

holidays/countries/germany.py (2)

26-29: Formatting improvements look good.

The minor formatting adjustments improve readability while maintaining the essential information about Germany's historical context.


243-248: Good conversion to Markdown-style bullet points.

The change from hyphenated list to Markdown bullet points improves readability and consistency with MkDocs formatting standards. The references remain intact and properly formatted as URLs.

holidays/countries/belarus.py (2)

34-36: Consistent Formatting for the "Cross-checked With" Section
The "Cross-checked With" section now follows a similar structured list format as the references section. This uniformity makes the documentation more approachable and easier to follow.


148-153: Enhanced Docstring for BelarusStaticHolidays
The updated docstring in the BelarusStaticHolidays class now features a clear header and structured reference list. This improvement helps maintain consistency across the documentation and supports the overall migration to Markdown-based documentation.

holidays/countries/thailand.py (2)

45-89: Docstring Formatting Enhanced: Consistent Markdown Links & Bullets
The references in the class docstring have been reformatted to use asterisk-based bullet points and proper markdown links. This not only improves readability but also enforces a consistent style across the documentation, aligning nicely with the MkDocs approach.


975-976: Static Holidays Docstring: Bullet Point Consistency
The bullet point for the HM Queen Rambai Barni's Royal Cremation Ceremony is now using an asterisk with a markdown link, which is consistent with the rest of the updated documentation. Nice work on harmonizing the formatting here!

holidays/countries/azerbaijan.py (4)

28-33: Clean docstring formatting for the Azerbaijan class.

The docstring formatting has been updated to use asterisk bullet points and angle brackets for URLs, which aligns well with Markdown standards. This improves readability in both code editors and generated documentation.


50-53: Good transition to Google-style docstring format.

You've successfully converted the parameter documentation from colon format to the Args section format, which is more readable and better supported by modern documentation generators like MkDocs.


265-278: Consistent reference formatting in AzerbaijanStaticHolidays class.

The references for substituted holidays have been updated to match the same formatting style as the main class, using asterisk bullet points and angle brackets for URLs. This consistency is important for maintainability.


280-280: Reference formatting aligned with documentation standards.

The special holidays reference follows the same pattern as other references, maintaining consistency across the entire file.

holidays/utils.py (6)

47-83: Well-structured conversion to Google-style docstrings for country_holidays function

The parameter documentation has been properly reformatted from reStructuredText format to Google-style, making it more readable and easier to maintain. The clear separation of "Args" and "Returns" sections follows best practices for Python documentation.


174-182: Good job using proper Markdown code block syntax

The code examples have been updated to use triple backticks for code blocks, which is the correct syntax for Markdown and will render properly in MkDocs.


218-244: Consistent docstring formatting in financial_holidays function

The parameter documentation for financial_holidays follows the same Google-style format as the other functions, maintaining consistency throughout the codebase.


274-275: Clear deprecation notice using Note section

The deprecation notice for CountryHoliday has been reformatted to use a "Note:" section, which aligns well with Google-style docstrings and makes the deprecation warning more visible.


287-294: Consistent formatting across all utility functions

All the utility functions (_list_localized_entities, list_localized_countries, list_localized_financial, _list_supported_entities, list_supported_countries, list_supported_financial) have been updated to use the same Google-style docstring format, which ensures consistency throughout the module.

Also applies to: 312-319, 328-334, 342-348, 362-368, 377-383


251-252:

Details

✅ Verification successful

Verify Markdown cross-references work with mkdocstrings

The reference to country_holidays using Markdown link syntax ([country_holidays()][holidays.utils.country_holidays]) is good, but ensure that this syntax works correctly with mkdocstrings for proper cross-referencing in the generated documentation.


🌐 Web query:

Does mkdocstrings support Markdown links for cross-references between functions?

💡 Result:

mkdocstrings fully supports using Markdown syntax for cross-references between functions and other documented elements. This capability is enabled through its integration with the autorefs plugin and specific syntax handling in documentation strings. Here's how it works:

Basic Cross-Reference Syntax

You can create cross-references using standard Markdown link syntax:

  • [link text][package.module.function] for explicit references
  • [package.module.function][] for implicit references using the identifier as link text

Example in a docstring:

def my_function():
    """See also [other_function][mypkg.mymodule.other_function]."""

Key Implementation Details

  1. Automatic Anchor Resolution:

    • mkdocstrings generates unique anchors for each documented object[3][4]
    • Links resolve to these anchors regardless of document structure changes[6][10]
  2. Autorefs Plugin Requirement:

    • Enable in mkdocs.yml:
      plugins:
        - search
        - autorefs
        - mkdocstrings
    • Allows cross-page linking without path knowledge[6][10]
  3. Relative References:

    • Use dot-relative syntax within modules:
      def method():
          """See [.sibling_method][] in same class."""
      ```[8][11]
  4. Type Annotation Linking:

    def process(items: list[mypkg.Item]) -> None:
        """Handles a list of [Item][mypkg.Item] objects."""

    Annotations automatically link to type definitions[3][11]

Advanced Features

  • Sub-heading Links: Reference sections within docstrings using object--heading syntax[4]
  • Intersphinx Support: Cross-reference external projects via Sphinx-compatible inventories[4]
  • Signature Cross-References: Link type annotations in function signatures when enabled[5]

Limitations

  • Requires explicit heading IDs via attr_list Markdown extension for custom anchors[1][6]
  • References must use fully qualified paths unless using relative syntax[8][11]

Example cross-page reference:

## API Documentation
See the [data processing][mypkg.processors.process_data] function for details.

This system enables robust cross-referencing while maintaining standard Markdown syntax compatibility[3][4][10].

Citations:


Markdown Cross-References Verified in Documentation

The Markdown link syntax [country_holidays()][holidays.utils.country_holidays] correctly leverages mkdocstrings’ support for cross-references—provided that the autorefs plugin is enabled in your mkdocs.yml configuration. No changes are needed in the code snippet, but please ensure that your mkdocs setup includes the necessary plugins for consistent documentation linking.

@github-actions github-actions bot added the l10n label Mar 26, 2025
@sonarqubecloud
Copy link
Copy Markdown

@arkid15r arkid15r requested a review from KJhellico March 26, 2025 19:22
@arkid15r
Copy link
Copy Markdown
Collaborator

Screenshot 2025-03-26 at 12 05 02 PM

🔥 🔥 🔥

@arkid15r arkid15r enabled auto-merge March 26, 2025 19:26
Copy link
Copy Markdown
Collaborator

@PPsyrius PPsyrius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@arkid15r arkid15r disabled auto-merge March 26, 2025 19:34
@arkid15r arkid15r merged commit a9fce3c into vacanza:dev Mar 26, 2025
32 of 33 checks passed
Copy link
Copy Markdown
Collaborator

@KJhellico KJhellico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Let's go! 🚀

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🔭 Outside diff range comments (1)
holidays/countries/mauritania.py (1)

40-54: ⚠️ Potential issue

Update undeclared variable with proper reference.

The code uses an undeclared year variable on line 53. This should be updated to use the instance variable self._year as used throughout the rest of the code.

- if year >= 1960:
+ if self._year >= 1960:
♻️ Duplicate comments (7)
holidays/countries/macau.py (1)

408-415: 🧹 Nitpick (assertive)

Markdown Link Formatting in Special Public and Government Holidays

The special holidays section uses angle brackets for URLs (lines 411 and 414) while the rest of the document uses standard Markdown link format [Link Text](URL). For consistency, consider using the standard Markdown format here as well.

-        * <https://www.io.gov.mo/pt/legis/rec/111020>
+        * [Macau Special Holidays](https://www.io.gov.mo/pt/legis/rec/111020)

-        * <https://www.dsal.gov.mo/pt/standard/holiday_table.html>
+        * [Special Mandatory Holidays](https://www.dsal.gov.mo/pt/standard/holiday_table.html)
holidays/financial/ny_stock_exchange.py (1)

37-46: 🧹 Nitpick (assertive)

Improved docstring structure with clear references section.

The docstring has been reformatted to follow Markdown conventions with URLs properly formatted in angle brackets. However, there's a minor inconsistency.

For complete consistency with the "References:" section, consider formatting "Historical data:" as a proper section heading by adding a blank line after it:

    References:
        * <https://www.nyse.com/publicdocs/nyse/regulation/nyse/NYSE_Rules.pdf>
        * <https://www.nyse.com/markets/hours-calendars>

    Historical data:
+
        * <https://s3.amazonaws.com/armstrongeconomics-wp/2013/07/NYSE-Closings.pdf>
        * <https://web.archive.org/web/20211101162021/https://www.nyse.com/markets/hours-calendars>
holidays/financial/brasil_bolsa_balcao.py (1)

31-33: 🧹 Nitpick (assertive)

Consider adding a blank line after Historical data heading

For improved visual separation and consistency with the References section, consider adding a blank line after the "Historical data:" header.

 Historical data:
+
        * [Feriados ANBIMA 2001-2099](https://www.anbima.com.br/feriados)
        * [Calendario de negociação B3](https://www.b3.com.br/pt_br/solucoes/plataformas/puma-trading-system/para-participantes-e-traders/calendario-de-negociacao/feriados)
holidays/countries/el_salvador.py (1)

20-25: 🧹 Nitpick (assertive)

Mixed reference formatting style.

The document now uses a mix of Markdown-style links and angle bracket URLs in the references section. While both are valid in Markdown, a consistent style would enhance readability.

Consider unifying the reference style by either:

  1. Using angle brackets for all URLs:
- * [Labor Code 1972](https://www.transparencia.gob.sv/institutions/gd-usulutan/documents/192280/download)
+ * <https://www.transparencia.gob.sv/institutions/gd-usulutan/documents/192280/download> (Labor Code 1972)
  1. Or using Markdown links for all:
- * <https://www.timeanddate.com/holidays/el-salvador>
+ * [Time and Date - El Salvador](https://www.timeanddate.com/holidays/el-salvador)
holidays/countries/san_marino.py (1)

21-21: 🧹 Nitpick (assertive)

Consider using proper Markdown link syntax.

The current reference format with angle brackets is not optimal Markdown syntax.

-        * <https://en.wikipedia.org/wiki/Public_holidays_in_San_Marino>
+        * [Public holidays in San Marino](https://en.wikipedia.org/wiki/Public_holidays_in_San_Marino)
holidays/countries/singapore.py (1)

306-311: 🧹 Nitpick (assertive)

Inconsistent URL formatting style.

There's an inconsistency in URL formatting between different docstrings in this file. The main Singapore class uses [text](url) format while this class uses angle brackets <url>.

Consider standardizing the URL formatting across all docstrings to maintain consistency.

-        * <https://www.mom.gov.sg/newsroom/press-releases/2015/sg50-public-holiday-on-7-august-2015>
-        * <https://www.straitstimes.com/singapore/politics/singapore-presidential-election-2023-polling-day-on-sept-1-nomination-day-on-aug-22>
+        * [MOM Press Release](https://www.mom.gov.sg/newsroom/press-releases/2015/sg50-public-holiday-on-7-august-2015)
+        * [Straits Times](https://www.straitstimes.com/singapore/politics/singapore-presidential-election-2023-polling-day-on-sept-1-nomination-day-on-aug-22)
holidays/countries/tanzania.py (1)

53-57: 🧹 Nitpick (assertive)

Limitations Section – Consider Consistent Bullet Usage

The limitations section uses an asterisk for the main bullet and hyphens for nested items. For maximum consistency in Markdown styling, consider using the same bullet marker (e.g., asterisks) for nested items as well.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1fa62c7 and 151809c.

📒 Files selected for processing (207)
  • .gitignore (1 hunks)
  • LICENSE (1 hunks)
  • docs/file_header.txt (1 hunks)
  • holidays/__init__.py (1 hunks)
  • holidays/calendars/__init__.py (1 hunks)
  • holidays/calendars/balinese_saka.py (2 hunks)
  • holidays/calendars/buddhist.py (1 hunks)
  • holidays/calendars/chinese.py (1 hunks)
  • holidays/calendars/custom.py (1 hunks)
  • holidays/calendars/gregorian.py (1 hunks)
  • holidays/calendars/hebrew.py (1 hunks)
  • holidays/calendars/hindu.py (1 hunks)
  • holidays/calendars/islamic.py (1 hunks)
  • holidays/calendars/julian.py (1 hunks)
  • holidays/calendars/julian_revised.py (1 hunks)
  • holidays/calendars/persian.py (1 hunks)
  • holidays/calendars/sinhala.py (1 hunks)
  • holidays/calendars/thai.py (1 hunks)
  • holidays/constants.py (1 hunks)
  • holidays/countries/__init__.py (1 hunks)
  • holidays/countries/afghanistan.py (3 hunks)
  • holidays/countries/albania.py (3 hunks)
  • holidays/countries/algeria.py (3 hunks)
  • holidays/countries/american_samoa.py (2 hunks)
  • holidays/countries/andorra.py (2 hunks)
  • holidays/countries/angola.py (2 hunks)
  • holidays/countries/argentina.py (2 hunks)
  • holidays/countries/armenia.py (2 hunks)
  • holidays/countries/aruba.py (2 hunks)
  • holidays/countries/australia.py (2 hunks)
  • holidays/countries/austria.py (2 hunks)
  • holidays/countries/azerbaijan.py (4 hunks)
  • holidays/countries/bahamas.py (2 hunks)
  • holidays/countries/bahrain.py (3 hunks)
  • holidays/countries/bangladesh.py (2 hunks)
  • holidays/countries/barbados.py (2 hunks)
  • holidays/countries/belarus.py (3 hunks)
  • holidays/countries/belgium.py (2 hunks)
  • holidays/countries/belize.py (2 hunks)
  • holidays/countries/bolivia.py (2 hunks)
  • holidays/countries/bosnia_and_herzegovina.py (3 hunks)
  • holidays/countries/botswana.py (2 hunks)
  • holidays/countries/brazil.py (2 hunks)
  • holidays/countries/brunei.py (3 hunks)
  • holidays/countries/bulgaria.py (2 hunks)
  • holidays/countries/burkina_faso.py (3 hunks)
  • holidays/countries/burundi.py (3 hunks)
  • holidays/countries/cambodia.py (2 hunks)
  • holidays/countries/cameroon.py (3 hunks)
  • holidays/countries/canada.py (2 hunks)
  • holidays/countries/chad.py (3 hunks)
  • holidays/countries/chile.py (2 hunks)
  • holidays/countries/china.py (2 hunks)
  • holidays/countries/colombia.py (2 hunks)
  • holidays/countries/congo.py (2 hunks)
  • holidays/countries/costa_rica.py (2 hunks)
  • holidays/countries/croatia.py (2 hunks)
  • holidays/countries/cuba.py (2 hunks)
  • holidays/countries/curacao.py (2 hunks)
  • holidays/countries/cyprus.py (2 hunks)
  • holidays/countries/czechia.py (2 hunks)
  • holidays/countries/denmark.py (2 hunks)
  • holidays/countries/djibouti.py (3 hunks)
  • holidays/countries/dominica.py (3 hunks)
  • holidays/countries/dominican_republic.py (2 hunks)
  • holidays/countries/ecuador.py (2 hunks)
  • holidays/countries/egypt.py (3 hunks)
  • holidays/countries/el_salvador.py (2 hunks)
  • holidays/countries/estonia.py (2 hunks)
  • holidays/countries/eswatini.py (2 hunks)
  • holidays/countries/ethiopia.py (3 hunks)
  • holidays/countries/finland.py (2 hunks)
  • holidays/countries/france.py (2 hunks)
  • holidays/countries/gabon.py (3 hunks)
  • holidays/countries/georgia.py (3 hunks)
  • holidays/countries/germany.py (3 hunks)
  • holidays/countries/ghana.py (3 hunks)
  • holidays/countries/greece.py (2 hunks)
  • holidays/countries/greenland.py (2 hunks)
  • holidays/countries/guam.py (2 hunks)
  • holidays/countries/guatemala.py (2 hunks)
  • holidays/countries/guernsey.py (3 hunks)
  • holidays/countries/haiti.py (2 hunks)
  • holidays/countries/honduras.py (3 hunks)
  • holidays/countries/hongkong.py (2 hunks)
  • holidays/countries/hungary.py (3 hunks)
  • holidays/countries/iceland.py (2 hunks)
  • holidays/countries/india.py (3 hunks)
  • holidays/countries/indonesia.py (4 hunks)
  • holidays/countries/iran.py (3 hunks)
  • holidays/countries/ireland.py (2 hunks)
  • holidays/countries/isle_of_man.py (2 hunks)
  • holidays/countries/israel.py (2 hunks)
  • holidays/countries/italy.py (2 hunks)
  • holidays/countries/jamaica.py (2 hunks)
  • holidays/countries/japan.py (2 hunks)
  • holidays/countries/jersey.py (3 hunks)
  • holidays/countries/jordan.py (3 hunks)
  • holidays/countries/kazakhstan.py (4 hunks)
  • holidays/countries/kenya.py (4 hunks)
  • holidays/countries/kuwait.py (3 hunks)
  • holidays/countries/kyrgyzstan.py (2 hunks)
  • holidays/countries/laos.py (2 hunks)
  • holidays/countries/latvia.py (2 hunks)
  • holidays/countries/lesotho.py (2 hunks)
  • holidays/countries/liechtenstein.py (2 hunks)
  • holidays/countries/lithuania.py (2 hunks)
  • holidays/countries/luxembourg.py (2 hunks)
  • holidays/countries/macau.py (3 hunks)
  • holidays/countries/madagascar.py (2 hunks)
  • holidays/countries/malawi.py (2 hunks)
  • holidays/countries/malaysia.py (3 hunks)
  • holidays/countries/maldives.py (2 hunks)
  • holidays/countries/malta.py (2 hunks)
  • holidays/countries/marshall_islands.py (2 hunks)
  • holidays/countries/mauritania.py (2 hunks)
  • holidays/countries/mexico.py (2 hunks)
  • holidays/countries/moldova.py (2 hunks)
  • holidays/countries/monaco.py (2 hunks)
  • holidays/countries/montenegro.py (3 hunks)
  • holidays/countries/morocco.py (3 hunks)
  • holidays/countries/mozambique.py (2 hunks)
  • holidays/countries/namibia.py (2 hunks)
  • holidays/countries/netherlands.py (2 hunks)
  • holidays/countries/new_zealand.py (2 hunks)
  • holidays/countries/nicaragua.py (2 hunks)
  • holidays/countries/nigeria.py (3 hunks)
  • holidays/countries/north_macedonia.py (2 hunks)
  • holidays/countries/northern_mariana_islands.py (2 hunks)
  • holidays/countries/norway.py (2 hunks)
  • holidays/countries/pakistan.py (2 hunks)
  • holidays/countries/palau.py (3 hunks)
  • holidays/countries/panama.py (2 hunks)
  • holidays/countries/papua_new_guinea.py (3 hunks)
  • holidays/countries/paraguay.py (2 hunks)
  • holidays/countries/peru.py (2 hunks)
  • holidays/countries/philippines.py (3 hunks)
  • holidays/countries/poland.py (2 hunks)
  • holidays/countries/portugal.py (2 hunks)
  • holidays/countries/puerto_rico.py (2 hunks)
  • holidays/countries/romania.py (2 hunks)
  • holidays/countries/russia.py (2 hunks)
  • holidays/countries/saint_kitts_and_nevis.py (3 hunks)
  • holidays/countries/saint_lucia.py (2 hunks)
  • holidays/countries/samoa.py (2 hunks)
  • holidays/countries/san_marino.py (2 hunks)
  • holidays/countries/saudi_arabia.py (3 hunks)
  • holidays/countries/serbia.py (2 hunks)
  • holidays/countries/seychelles.py (3 hunks)
  • holidays/countries/singapore.py (4 hunks)
  • holidays/countries/slovakia.py (2 hunks)
  • holidays/countries/slovenia.py (2 hunks)
  • holidays/countries/south_africa.py (2 hunks)
  • holidays/countries/south_korea.py (3 hunks)
  • holidays/countries/spain.py (3 hunks)
  • holidays/countries/sri_lanka.py (4 hunks)
  • holidays/countries/sweden.py (2 hunks)
  • holidays/countries/switzerland.py (2 hunks)
  • holidays/countries/taiwan.py (3 hunks)
  • holidays/countries/tanzania.py (3 hunks)
  • holidays/countries/thailand.py (3 hunks)
  • holidays/countries/timor_leste.py (3 hunks)
  • holidays/countries/tonga.py (3 hunks)
  • holidays/countries/tunisia.py (2 hunks)
  • holidays/countries/turkey.py (3 hunks)
  • holidays/countries/tuvalu.py (2 hunks)
  • holidays/countries/ukraine.py (3 hunks)
  • holidays/countries/united_arab_emirates.py (4 hunks)
  • holidays/countries/united_kingdom.py (2 hunks)
  • holidays/countries/united_states.py (2 hunks)
  • holidays/countries/united_states_minor_outlying_islands.py (2 hunks)
  • holidays/countries/united_states_virgin_islands.py (2 hunks)
  • holidays/countries/uruguay.py (2 hunks)
  • holidays/countries/uzbekistan.py (3 hunks)
  • holidays/countries/vanuatu.py (2 hunks)
  • holidays/countries/vatican_city.py (2 hunks)
  • holidays/countries/venezuela.py (2 hunks)
  • holidays/countries/vietnam.py (3 hunks)
  • holidays/countries/zambia.py (2 hunks)
  • holidays/countries/zimbabwe.py (2 hunks)
  • holidays/deprecations/v1_incompatibility.py (1 hunks)
  • holidays/financial/__init__.py (1 hunks)
  • holidays/financial/brasil_bolsa_balcao.py (2 hunks)
  • holidays/financial/european_central_bank.py (2 hunks)
  • holidays/financial/ice_futures_europe.py (2 hunks)
  • holidays/financial/ny_stock_exchange.py (3 hunks)
  • holidays/groups/__init__.py (1 hunks)
  • holidays/groups/balinese_saka.py (1 hunks)
  • holidays/groups/buddhist.py (1 hunks)
  • holidays/groups/chinese.py (1 hunks)
  • holidays/groups/christian.py (1 hunks)
  • holidays/groups/custom.py (1 hunks)
  • holidays/groups/eastern.py (1 hunks)
  • holidays/groups/hebrew.py (1 hunks)
  • holidays/groups/hindu.py (1 hunks)
  • holidays/groups/international.py (1 hunks)
  • holidays/groups/islamic.py (1 hunks)
  • holidays/groups/persian.py (1 hunks)
  • holidays/groups/sinhala.py (1 hunks)
  • holidays/groups/thai.py (1 hunks)
  • holidays/helpers.py (1 hunks)
  • holidays/holiday_base.py (19 hunks)
  • holidays/locale/am/LC_MESSAGES/ET.po (1 hunks)
  • holidays/locale/ar/LC_MESSAGES/AE.po (1 hunks)
  • holidays/locale/ar/LC_MESSAGES/BH.po (1 hunks)
  • holidays/locale/ar/LC_MESSAGES/CA.po (1 hunks)
  • holidays/locale/ar/LC_MESSAGES/DJ.po (1 hunks)
⛔ Files not processed due to max files limit (61)
  • holidays/locale/ar/LC_MESSAGES/DZ.po
  • holidays/locale/ar/LC_MESSAGES/EG.po
  • holidays/locale/ar/LC_MESSAGES/ET.po
  • holidays/locale/ar/LC_MESSAGES/JO.po
  • holidays/locale/ar/LC_MESSAGES/KW.po
  • holidays/locale/ar/LC_MESSAGES/MA.po
  • holidays/locale/ar/LC_MESSAGES/SA.po
  • holidays/locale/ar/LC_MESSAGES/TN.po
  • holidays/locale/ar/LC_MESSAGES/UA.po
  • holidays/locale/az/LC_MESSAGES/AZ.po
  • holidays/locale/be/LC_MESSAGES/BY.po
  • holidays/locale/bg/LC_MESSAGES/BG.po
  • holidays/locale/bs/LC_MESSAGES/BA.po
  • holidays/locale/cnr/LC_MESSAGES/ME.po
  • holidays/locale/cs/LC_MESSAGES/CZ.po
  • holidays/locale/da/LC_MESSAGES/DK.po
  • holidays/locale/da/LC_MESSAGES/GL.po
  • holidays/locale/de/LC_MESSAGES/AT.po
  • holidays/locale/de/LC_MESSAGES/BE.po
  • holidays/locale/de/LC_MESSAGES/CH.po
  • holidays/locale/de/LC_MESSAGES/DE.po
  • holidays/locale/de/LC_MESSAGES/LI.po
  • holidays/locale/de/LC_MESSAGES/LU.po
  • holidays/locale/de/LC_MESSAGES/PL.po
  • holidays/locale/el/LC_MESSAGES/CY.po
  • holidays/locale/el/LC_MESSAGES/GR.po
  • holidays/locale/en_AU/LC_MESSAGES/AU.po
  • holidays/locale/en_CA/LC_MESSAGES/CA.po
  • holidays/locale/en_CY/LC_MESSAGES/CY.po
  • holidays/locale/en_GB/LC_MESSAGES/GB.po
  • holidays/locale/en_GB/LC_MESSAGES/IM.po
  • holidays/locale/en_GB/LC_MESSAGES/TV.po
  • holidays/locale/en_HK/LC_MESSAGES/HK.po
  • holidays/locale/en_IN/LC_MESSAGES/IN.po
  • holidays/locale/en_KE/LC_MESSAGES/KE.po
  • holidays/locale/en_LC/LC_MESSAGES/LC.po
  • holidays/locale/en_MO/LC_MESSAGES/MO.po
  • holidays/locale/en_PH/LC_MESSAGES/PH.po
  • holidays/locale/en_SC/LC_MESSAGES/SC.po
  • holidays/locale/en_SG/LC_MESSAGES/SG.po
  • holidays/locale/en_US/LC_MESSAGES/AE.po
  • holidays/locale/en_US/LC_MESSAGES/AF.po
  • holidays/locale/en_US/LC_MESSAGES/AL.po
  • holidays/locale/en_US/LC_MESSAGES/AM.po
  • holidays/locale/en_US/LC_MESSAGES/AO.po
  • holidays/locale/en_US/LC_MESSAGES/AR.po
  • holidays/locale/en_US/LC_MESSAGES/AT.po
  • holidays/locale/en_US/LC_MESSAGES/AU.po
  • holidays/locale/en_US/LC_MESSAGES/AW.po
  • holidays/locale/en_US/LC_MESSAGES/AZ.po
  • holidays/locale/en_US/LC_MESSAGES/BA.po
  • holidays/locale/en_US/LC_MESSAGES/BE.po
  • holidays/locale/en_US/LC_MESSAGES/BG.po
  • holidays/locale/en_US/LC_MESSAGES/BH.po
  • holidays/locale/en_US/LC_MESSAGES/BN.po
  • holidays/locale/en_US/LC_MESSAGES/BO.po
  • holidays/locale/en_US/LC_MESSAGES/BR.po
  • holidays/locale/en_US/LC_MESSAGES/BVMF.po
  • holidays/locale/en_US/LC_MESSAGES/BY.po
  • holidays/locale/en_US/LC_MESSAGES/CA.po
  • holidays/locale/en_US/LC_MESSAGES/CG.po
🧰 Additional context used
🧠 Learnings (1)
holidays/countries/united_states.py (1)
Learnt from: KJhellico
PR: vacanza/holidays#2289
File: holidays/countries/united_states.py:35-84
Timestamp: 2025-03-26T17:15:40.859Z
Learning: In Markdown documentation, when a state or entity has multiple hyperlinks, it should be formatted with a main bullet for the entity followed by sub-bullets for each link, rather than encapsulating the entity name in square brackets as is done for entities with single hyperlinks.
🔇 Additional comments (475)
holidays/countries/uruguay.py (3)

7-7: Correctly updated reference to AUTHORS.md file

This change properly references the file extension, ensuring consistency with the migration to Markdown-based documentation.


27-28: Clean and concise class introduction

The docstring provides a clear, concise introduction to the Uruguay holidays class, following the standardized format being applied across the project.


30-36: Properly formatted references with Markdown bullet points

The references section has been updated to use asterisks for bullet points, which is the standard Markdown syntax. This change aligns with the MkDocs migration and improves documentation consistency.

holidays/countries/macau.py (3)

7-7: Documentation reference update looks good.

Updated reference from "AUTHORS file" to "AUTHORS.md file" is consistent with the project's migration to Markdown documentation.


37-61: Documentation format looks clean and well-structured.

The Markdown formatting for the class documentation is well-organized with a clear introduction followed by properly formatted reference links. This aligns well with the documentation migration objectives.


417-418: LGTM! Cross-checking links properly formatted.

The cross-checking links are properly formatted using standard Markdown link format.

LICENSE (1)

1-1: Consistent Attribution Update in LICENSE

The update to reference AUTHORS.md file is correct and ensures consistency with the new documentation standards. Great job on this neat change!

holidays/__init__.py (1)

7-9: Consistent Change in Author Reference

Changing the comment to reference AUTHORS.md file aligns well with the repository-wide update. This change removes ambiguity and maintains uniformity across the project.

docs/file_header.txt (1)

7-7: Updated Documentation Header

The header now correctly refers to AUTHORS.md file, keeping the documentation consistent with the overall project updates. Nice and clear!

.gitignore (1)

17-17: Excluding Generated Documentation Files

The addition of docs/auto_gen_files/ and site/ to .gitignore is a smart move. This will prevent generated files from cluttering the repository, aligning with the migration to MkDocs. Excellent update!

Also applies to: 24-24

holidays/calendars/islamic.py (1)

7-7: Doc Update: Corrected Authors Reference
The comment now clearly points to AUTHORS.md file instead of the ambiguous “AUTHORS file,” ensuring consistency and clarity with the rest of the project’s documentation.

holidays/countries/zimbabwe.py (2)

7-7: Good update to reference AUTHORS.md file

The update to reference the AUTHORS.md file aligns with the migration from Sphinx to MkDocs.


18-22: Well-structured docstring format

The docstring has been reformatted following a clean pattern with a concise description followed by properly formatted references using angle brackets. This follows best practices for Markdown documentation.

holidays/countries/tuvalu.py (3)

7-7: Good update to reference AUTHORS.md file

The update to reference the AUTHORS.md file aligns with the migration from Sphinx to MkDocs.


24-24: Concise class description added

The addition of a clear, concise description "Tuvalu holidays." improves documentation clarity.


27-35: Improved reference formatting

The references section has been reformatted from hyphenated lists to properly formatted Markdown links, enhancing readability while maintaining all the necessary information.

holidays/countries/pakistan.py (3)

7-7: Good update to reference AUTHORS.md file

The update to reference the AUTHORS.md file aligns with the migration from Sphinx to MkDocs.


20-20: Concise class description added

The addition of a clear, concise description "Pakistan holidays." improves documentation clarity.


27-30: Improved parameter documentation format

The parameter documentation has been reformatted from :param style to Google-style Args: format with proper indentation and line breaks, which aligns with the PR objective of standardizing docstrings to Google-style.

holidays/countries/new_zealand.py (2)

7-7: Good update to reference AUTHORS.md file

The update to reference the AUTHORS.md file aligns with the migration from Sphinx to MkDocs.


27-27: Concise class description added

The addition of a clear, concise description "New Zealand holidays." improves documentation clarity.

holidays/countries/tunisia.py (2)

7-7: Consistent reference to AUTHORS.md file

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency across documentation references.


30-33: Improved docstring format with Google-style structure

The restructured docstring using "Args:" format enhances readability while maintaining the same content. This aligns with the PR objective of converting docstrings to Google-style format.

holidays/countries/austria.py (2)

7-7: Consistent reference to AUTHORS.md file

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency across documentation references.


21-21: Added descriptive class docstring

The addition of "Austria holidays." docstring provides a clear, concise description of the class purpose.

holidays/countries/mozambique.py (2)

7-7: Consistent reference to AUTHORS.md file

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency across documentation references.


20-21: Docstring Enhancement for Mozambique

The addition of the concise docstring "Mozambique holidays." for the Mozambique class effectively improves clarity in the documentation. It aligns well with our overall goal of enhancing documentation quality across the project.

holidays/countries/estonia.py (2)

7-7: Consistent reference to AUTHORS.md file

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency across documentation references.


20-21: Added descriptive class docstring

The addition of "Estonia holidays." docstring provides a clear, concise description of the class purpose.

holidays/countries/afghanistan.py (3)

7-7: Consistent documentation reference update.

The reference to the AUTHORS file has been updated to "AUTHORS.md file" to align with the new Markdown documentation approach.


36-41: Improved docstring structure with clear references section.

The docstring has been reformatted to follow Markdown conventions with:

  • A concise title "Afghanistan holidays"
  • A dedicated "References:" section
  • Properly formatted URLs as bullet points with angle brackets

This enhancement improves readability and aligns with the MkDocs migration goals.


55-58: Parameter documentation standardized to Google-style format.

The parameter documentation has been updated from :param style to the more structured Google-style with:

  • An "Args:" section header
  • Consistent indentation for the parameter description
  • Clear formatting that separates the parameter name from its description

This change supports better documentation generation with MkDocs.

holidays/financial/ny_stock_exchange.py (2)

7-7: Consistent documentation reference update.

The reference to the AUTHORS file has been updated to "AUTHORS.md file" to align with the new Markdown documentation approach.


152-156: Consistent docstring formatting for the StaticHolidays class.

The docstring has been properly updated to follow the same Markdown conventions as the main class, with a clear title and references section.

holidays/countries/zambia.py (2)

7-7: Consistent documentation reference update.

The reference to the AUTHORS file has been updated to "AUTHORS.md file" to align with the new Markdown documentation approach.


19-25: Improved docstring structure with clear references section.

The docstring has been reformatted to follow Markdown conventions with:

  • A concise title "Zambia holidays"
  • A dedicated "References:" section
  • Properly formatted URLs as bullet points with angle brackets

This enhancement improves readability and aligns with the MkDocs migration goals.

holidays/countries/uzbekistan.py (2)

7-7: Consistent documentation reference update.

The reference to the AUTHORS file has been updated to "AUTHORS.md file" to align with the new Markdown documentation approach.


44-47: Parameter documentation standardized to Google-style format.

The parameter documentation has been updated from :param style to the more structured Google-style with:

  • An "Args:" section header
  • Consistent indentation for the parameter description
  • Clear formatting that separates the parameter name from its description

This change supports better documentation generation with MkDocs.

holidays/countries/egypt.py (2)

22-22: Consider preserving contextual information in docstring

The simplified docstring matches the new style but removes valuable context that was previously provided about holidays being estimates and certain holidays having moving dates. Consider preserving this information within the new documentation format.

-"""Egypt holidays."""
+"""Egypt holidays.

Holidays here are estimates. For the sake of simplicity dates temporarily 
assigned every year to a subset of Islamic holidays have not been considered.
"""

33-37: The parameter documentation looks good

The documentation format has been updated to use the more structured "Args:" style which improves readability and consistency across the codebase.

holidays/countries/djibouti.py (2)

21-22: The docstring addition looks good

Adding a clear class docstring improves code readability and documentation.


34-38: The parameter documentation looks good

The documentation format has been updated to use the more structured "Args:" style which improves readability and consistency across the codebase.

holidays/countries/american_samoa.py (1)

18-22: Improved docstring formatting

The change from a comment to a proper docstring with better formatting enhances readability and follows documentation best practices. The URL formatting with angle brackets is also a good improvement.

holidays/countries/honduras.py (3)

7-7: Updated Author Reference
The file now correctly references AUTHORS.md, ensuring consistency in acknowledging contributors.


20-25: Enhanced Class Docstring Format
The updated docstring now uses structured references (with bullet points and clear URL formatting) to provide quick access to relevant legal documents. This improves readability and aligns with the documentation style goals.


58-58: Concise Holiday Reference Comment
Switching the full URL to a short reference ("Decree 78-2015.") makes the comment more succinct while still informative.

holidays/countries/puerto_rico.py (2)

7-7: Updated Author Reference
The header now points to AUTHORS.md, which is consistent with the project-wide update.


18-22: Clear Class Docstring
The revised docstring for HolidaysPR clearly defines its functionality and includes an external link for additional context, enhancing clarity and uniformity.

holidays/countries/northern_mariana_islands.py (2)

7-7: Updated Author Reference
The header correctly references AUTHORS.md, maintaining the project's updated documentation standards.


18-22: Improved Class Docstring
The new docstring for HolidaysMP clearly describes the purpose of the class and includes a well-formatted external link. Great job on standardizing the format!

holidays/groups/international.py (1)

7-7: Standardized Author Attribution
Updating the header to reference AUTHORS.md ensures consistency across the codebase without affecting functionality.

holidays/groups/__init__.py (1)

7-7: Consistent Author Attribution Update
The reference now points to AUTHORS.md, which keeps the contributor acknowledgments up-to-date and consistent throughout the repository.

holidays/locale/ar/LC_MESSAGES/CA.po (1)

7-7: Consistent Authors Reference Update
The comment has been updated to reference "AUTHORS.md file" instead of "AUTHORS file", ensuring consistency with the rest of the documentation changes. This is a straightforward documentation update with no functional impact.

holidays/groups/thai.py (1)

7-7: Uniform Documentation Reference
The authorship comment now correctly points to "AUTHORS.md file", aligning with other updates across the project. The change improves clarity and consistency without affecting functionality.

holidays/locale/ar/LC_MESSAGES/DJ.po (1)

7-7: Updated Authorship Attribution
The reference to the authors documentation has been updated to "AUTHORS.md file", matching the standardized format across the codebase. This change is purely cosmetic and helps maintain consistency throughout.

holidays/helpers.py (1)

7-7: Documentation Comment Update
The header comment now reflects "AUTHORS.md file" for authorship information, which is consistent with recent updates in other files. No issues here—nice and clear!

holidays/groups/custom.py (1)

7-7: Consistent Authors Reference
The top-of-file comment has been updated to reference "AUTHORS.md file", ensuring uniformity across the project’s documentation. This is a clean, non-functional update that improves clarity.

holidays/locale/ar/LC_MESSAGES/AE.po (1)

7-7: Standardized Authorship Reference Updated
Nice work updating the authorship comment to "AUTHORS.md file" for consistency. This helps keep our documentation unified!

holidays/locale/am/LC_MESSAGES/ET.po (1)

7-7: Consistent Documentation Reference
The change to "AUTHORS.md file" ensures that our attribution references are uniform across localization files. Great job!

holidays/calendars/julian.py (1)

7-7: Updated Authorship Comment in Julian Calendar
Updating the reference to "AUTHORS.md file" is a solid move to standardize our documentation. Everything looks clean here.

holidays/calendars/julian_revised.py (1)

7-7: Uniform Attribution Reference
Changing the comment to "AUTHORS.md file" aligns with our project-wide documentation update. This is a nice, clear update.

holidays/calendars/custom.py (1)

7-7: Consistent Authors Reference in Custom Calendar
The update to "AUTHORS.md file" in the custom calendar file's header ensures our documentation attribution is consistent project-wide. Well done!

holidays/groups/persian.py (1)

7-7: Consistent Authorship Reference:
The updated comment now references the "AUTHORS.md file" rather than the generic "AUTHORS file". This small but important change improves consistency across the project's documentation.

holidays/financial/__init__.py (1)

7-7: Standardized Documentation Reference:
Changing the text to reference "AUTHORS.md file" helps maintain uniformity in the header comments. This is a clean update that aligns well with the overall documentation migration goals.

holidays/groups/hebrew.py (1)

7-7: Uniform Authorship Attribution:
Updating the authorship comment to "AUTHORS.md file" ensures consistency across the codebase. It’s a straightforward but valuable documentation improvement.

holidays/groups/hindu.py (1)

7-7: Documentation Update for Authorship:
The change from "AUTHORS file" to "AUTHORS.md file" in the header is a clear improvement that standardizes our references, aligning with the new documentation practices.

holidays/groups/christian.py (1)

7-7: Refined Authorship Reference:
This update replaces "AUTHORS file" with "AUTHORS.md file," achieving a more current and consistent reference across our headers. Nice work keeping our documentation up-to-date!

holidays/groups/balinese_saka.py (1)

7-7: Documentation Consistency Update:
The comment now correctly references "AUTHORS.md file" instead of the old "AUTHORS file." This clear and consistent update enhances the overall documentation.

holidays/groups/sinhala.py (1)

7-7: Consistent Authorship Reference:
The header comment has been updated to use "AUTHORS.md file," which aligns with the documentation standard across the codebase. Nice and straightforward!

holidays/calendars/buddhist.py (1)

7-7: Updated Authors Reference:
Changing the reference to "AUTHORS.md file" here ensures that our documentation is consistent and clear. This textual update is spot on.

holidays/calendars/hindu.py (1)

7-7: Refined Documentation Notice:
The comment now mentions "AUTHORS.md file," which is a welcome update for clarity and consistency. The change is perfectly in line with the new documentation style.

holidays/calendars/__init__.py (1)

7-7: Uniform Documentation Update:
Updating the authorship line to "AUTHORS.md file" here brings uniformity across our modules. This improvement in the comments is both clear and helpful.

holidays/constants.py (1)

7-7: Authorship Reference Update Confirmed
The update from "AUTHORS file" to "AUTHORS.md file" improves clarity and maintains consistency with the rest of the repository's documentation.

holidays/groups/chinese.py (1)

7-7: Comment Consistency Update
The header comment now correctly points to "AUTHORS.md file." This change is simple and promotes consistency across the project documentation.

holidays/deprecations/v1_incompatibility.py (1)

7-7: Updated Authorship Attribution
The header now references "AUTHORS.md file" instead of the old format. This is a clear and uniform update across the codebase and does not affect any functionality.

holidays/groups/buddhist.py (1)

7-7: Standardized Authorship Comment
The modification in the header comment to reference "AUTHORS.md file" aligns with similar updates across the repository. Nice work on keeping the documentation consistent!

holidays/countries/__init__.py (1)

7-7: Uniform Documentation Reference
The updated comment now correctly tells users to refer to "AUTHORS.md file." This ensures clarity and consistency throughout the project’s source files.

holidays/calendars/gregorian.py (1)

7-7: Consistent Authors Update:
The authorship comment has been updated to reference "AUTHORS.md file" instead of the generic "AUTHORS file". This small change improves clarity and aligns with the broader documentation migration.

holidays/calendars/persian.py (1)

7-7: Refined Authorship Attribution:
The update now clearly points to "AUTHORS.md file" for contributor details. This adjustment keeps the documentation uniform across the project.

holidays/groups/eastern.py (1)

7-7: Updated Authors Reference:
The authorship note now accurately refers to "AUTHORS.md file", ensuring consistency with other documentation updates.

holidays/locale/ar/LC_MESSAGES/BH.po (1)

7-7: Localized Authorship Reference Update:
The comment now directs users to "AUTHORS.md file", which is consistent with the recent documentation revamp. This update is clear, precise, and helpful for future contributors.

holidays/groups/islamic.py (1)

7-7: Uniform Authorship Documentation:
The authorship comment has been revised to mention "AUTHORS.md file". This minor yet important change reinforces consistency across our codebase and documentation.

holidays/calendars/sinhala.py (1)

7-7: Consistent filename update from AUTHORS to AUTHORS.md

This change aligns with the migration from Sphinx to MkDocs, standardizing file references to use the Markdown extension.

holidays/countries/curacao.py (2)

7-7: Consistent filename update from AUTHORS to AUTHORS.md

This change aligns with the migration from Sphinx to MkDocs, standardizing file references to use the Markdown extension.


23-27: Improved docstring formatting for better MkDocs compatibility

The docstring has been standardized with a clear title and properly formatted references section. The angle brackets around URLs will help MkDocs render them as clickable links.

holidays/countries/russia.py (2)

7-7: Consistent filename update from AUTHORS to AUTHORS.md

This change aligns with the migration from Sphinx to MkDocs, standardizing file references to use the Markdown extension.


22-26: Improved docstring formatting for better MkDocs compatibility

The docstring has been standardized with a clear title and properly formatted references section. The angle brackets around URLs will help MkDocs render them as clickable links.

holidays/countries/canada.py (2)

7-7: Consistent filename update from AUTHORS to AUTHORS.md

This change aligns with the migration from Sphinx to MkDocs, standardizing file references to use the Markdown extension.


31-43: Improved docstring formatting for better MkDocs compatibility

The docstring has been standardized with a clear title and properly formatted references. The angle brackets around URLs will help MkDocs render them as clickable links.

holidays/countries/botswana.py (2)

7-7: Documentation enhancement: Updated AUTHORS reference.

The change to reference "AUTHORS.md file" instead of "AUTHORS file" improves consistency with the migration to Markdown documentation format.


24-30: Good restructuring of the documentation format.

The docstring has been nicely restructured with:

  • Clear title "Botswana holidays."
  • Well-organized "References:" section
  • Properly formatted URLs with angle brackets for better compatibility with MkDocs

This change aligns well with the PR objective of migrating from Sphinx to MkDocs.

holidays/countries/finland.py (2)

7-7: Documentation enhancement: Updated AUTHORS reference.

The change to reference "AUTHORS.md file" instead of "AUTHORS file" improves consistency with the migration to Markdown documentation format.


22-32: Effective docstring reformatting with improved link handling.

The changes to the docstring enhance readability with:

  • Clear title "Finland holidays."
  • Consistent formatting for URL references using angle brackets
  • Well-structured Markdown-style links for items like "Bank holidays" in different languages

This format works well with both MkDocs and GitHub's Markdown rendering.

holidays/countries/brazil.py (2)

7-7: Documentation enhancement: Updated AUTHORS reference.

The change to reference "AUTHORS.md file" instead of "AUTHORS file" improves consistency with the migration to Markdown documentation format.


23-30: Well-structured documentation with mixed link formatting.

The docstring format has been effectively updated with:

  • Clear title "Brazil holidays."
  • Consistent References section
  • Mixed formatting approach with both angle brackets and Markdown-style links

This mixed approach appropriately handles both simple URLs and links with descriptive text.

holidays/financial/european_central_bank.py (2)

7-7: Documentation enhancement: Updated AUTHORS reference.

The change to reference "AUTHORS.md file" instead of "AUTHORS file" improves consistency with the migration to Markdown documentation format.


19-25: Clean, consistent docstring formatting.

The docstring has been effectively reformatted with:

  • Clear title "European Central Bank holidays."
  • Well-organized References section with consistent URL formatting
  • Proper angle bracket syntax for URLs that works well with MkDocs

This change maintains a consistent style with other modules in the codebase.

holidays/countries/czechia.py (1)

7-7: Standardized documentation format

The changes properly align with the Google-style docstrings mentioned in the PR objectives. The updated format with a clear title sentence followed by organized references using bullet points improves readability while maintaining all essential information.

Also applies to: 20-26

holidays/countries/united_kingdom.py (1)

7-7: Documentation format aligned with project standards

The changes follow the consistent pattern of documentation standardization across the codebase. The clear title sentence and well-formatted reference links make the documentation more accessible.

Also applies to: 27-33

holidays/countries/marshall_islands.py (1)

7-7: Documentation structure improved

The documentation now follows a more structured format with a clear title and properly formatted references section. This matches the patterns seen in other country modules and improves overall consistency.

Also applies to: 21-25

holidays/countries/malta.py (1)

7-7: Documentation standardization properly implemented

The changes successfully convert the documentation to the Google-style format with a clear title and properly structured references section. The formatting of reference links with explicit markdown syntax enhances readability.

Also applies to: 20-28

holidays/countries/namibia.py (2)

7-7: Good documentation update!

The AUTHORS reference has been updated to point to AUTHORS.md file, which aligns with the documentation migration from Sphinx to MkDocs.


19-24: Documentation format improved!

The docstring has been nicely reformatted to follow Markdown conventions with:

  • Clear "Namibia holidays." title
  • Structured "References:" section
  • Bullet points using asterisks instead of hyphens
  • URLs enclosed in angle brackets for better rendering in MkDocs

These changes align well with the migration from Sphinx to MkDocs.

holidays/countries/taiwan.py (3)

7-7: Good documentation update!

The AUTHORS reference has been updated to point to AUTHORS.md file, aligning with the documentation migration.


48-69: Well-structured documentation format!

The Taiwan class docstring has been nicely reformatted with:

  • Clean "Taiwan holidays." title
  • Organized "References:" section with proper Markdown formatting
  • URLs properly enclosed in angle brackets
  • Ministry of Interior Orders using Markdown-style links instead of raw URLs

These formatting improvements will render much better in MkDocs.


267-297: Consistent documentation formatting!

The TaiwanStaticHolidays documentation has been updated to match the same formatting standard as the main class, with proper Markdown formatting for all DGPA Work Calendar links.

holidays/countries/madagascar.py (2)

7-7: Good documentation update!

The AUTHORS reference has been updated to point to AUTHORS.md file, consistent with other files.


21-25: Documentation format improved!

The docstring has been reformatted with a clear title and properly formatted references using Markdown conventions.

holidays/countries/denmark.py (2)

7-7: Good documentation update!

The AUTHORS reference has been updated to point to AUTHORS.md file, consistent with other files in this PR.


21-26: Documentation format improved!

The docstring has been reformatted to follow standard Markdown conventions:

  • Clear title line
  • Structured references section
  • URLs enclosed in angle brackets for better rendering

These changes will display correctly in MkDocs and improve overall documentation consistency.

holidays/countries/bangladesh.py (2)

7-7: File reference updated to include file extension

The file reference has been updated from "AUTHORS file" to "AUTHORS.md file", which is more precise and follows Markdown conventions.


19-23: Docstring formatting improved for Markdown compatibility

The changes to the docstring follow good Markdown practices:

  1. Added a clear, concise introduction: "Bangladesh holidays."
  2. Converted reference links from hyphen bullets to asterisk bullets
  3. Added angle brackets around URLs for proper Markdown link formatting

These changes align with the migration from Sphinx to MkDocs and improve documentation readability.

holidays/countries/netherlands.py (2)

7-7: File reference updated to include file extension

The file reference has been updated from "AUTHORS file" to "AUTHORS.md file", which is more precise and follows Markdown conventions.


23-28: Docstring formatting improved for Markdown compatibility

The changes to the docstring follow good Markdown practices:

  1. Added a clear, concise introduction: "Netherlands holidays."
  2. Converted reference links from hyphen bullets to asterisk bullets
  3. Added angle brackets around URLs for proper Markdown link formatting

These changes align with the migration from Sphinx to MkDocs and improve documentation readability.

holidays/countries/switzerland.py (2)

7-7: File reference updated to include file extension

The file reference has been updated from "AUTHORS file" to "AUTHORS.md file", which is more precise and follows Markdown conventions.


22-27: Docstring formatting improved for Markdown compatibility

The changes to the docstring follow good Markdown practices:

  1. Added a clear, concise introduction: "Switzerland holidays."
  2. Converted reference links from hyphen bullets to asterisk bullets
  3. Added angle brackets around URLs for proper Markdown link formatting

These changes align with the migration from Sphinx to MkDocs and improve documentation readability.

holidays/countries/angola.py (2)

7-7: File reference updated to include file extension

The file reference has been updated from "AUTHORS file" to "AUTHORS.md file", which is more precise and follows Markdown conventions.


28-42: Docstring formatting improved with enhanced Markdown formatting

The changes to the docstring show excellent Markdown practices:

  1. Added a clear, concise introduction: "Angola holidays."
  2. Converted reference links from hyphen bullets to asterisk bullets
  3. Used a mix of angle bracket URLs and proper Markdown link syntax [text](url)

This implementation is particularly well done as it demonstrates both link formatting styles available in Markdown. The mixed approach works well with MkDocs while maintaining compatibility with GitHub's Markdown renderer.

holidays/countries/liechtenstein.py (3)

7-7: Documentation update aligned with project standards.

The reference to the AUTHORS file has been properly updated to "AUTHORS.md file" for consistency across the project.


21-22: Clean docstring format compliant with MkDocs style.

The class docstring now directly starts with "Liechtenstein holidays." without unnecessary line breaks, improving readability and consistency.


24-25: References properly formatted for Markdown compatibility.

The references section now uses asterisks for bullet points and angle brackets around URLs, which follows Markdown best practices and improves rendering in MkDocs.

holidays/countries/latvia.py (2)

7-7: Documentation update aligned with project standards.

The reference to the AUTHORS file has been properly updated to "AUTHORS.md file" for consistency across the project.


21-27: Well-structured docstring following Markdown conventions.

The docstring has been reformatted to follow a consistent pattern with a clear introductory line and properly formatted references using Markdown bullet points and URL formatting.

holidays/countries/bahrain.py (4)

7-7: Documentation update aligned with project standards.

The reference to the AUTHORS file has been properly updated to "AUTHORS.md file" for consistency across the project.


22-22: Clean docstring format compliant with MkDocs style.

The class docstring now directly starts with "Bahrain holidays." improving readability and consistency with other country modules.


25-26: References properly formatted for Markdown compatibility.

The references section now uses asterisks for bullet points and angle brackets around URLs, following Markdown best practices for MkDocs.


38-41: Improved parameter documentation format.

The parameter documentation has been updated from :param style to the more readable "Args:" format with proper indentation and line breaks, enhancing clarity.

holidays/countries/cameroon.py (4)

7-7: Documentation update aligned with project standards.

The reference to the AUTHORS file has been properly updated to "AUTHORS.md file" for consistency across the project.


27-28: Clean docstring format compliant with MkDocs style.

The class docstring now starts with "Cameroon holidays." followed by an appropriate line break, maintaining a consistent format with other country modules.


30-32: References properly formatted for Markdown compatibility.

The references section now uses asterisks for bullet points and angle brackets around URLs, which follows Markdown best practices and improves rendering in MkDocs.


42-45: Improved parameter documentation format.

The parameter documentation has been updated from :param style to the more readable "Args:" format with proper indentation and line breaks, enhancing clarity.

holidays/countries/seychelles.py (3)

7-7: Consistent update to AUTHORS reference format

The update from "AUTHORS file" to "AUTHORS.md file" follows the migration to Markdown documentation format.


21-28: Documentation improvement with proper Markdown formatting

The docstring has been enhanced with:

  1. A clear introductory line "Seychelles holidays."
  2. Explicit "References:" section heading
  3. Well-formatted Markdown links using angle brackets and bullet points

These changes align well with the MkDocs migration goals and improve readability.


120-132: Consistent Markdown formatting in static holidays class docstring

The documentation for SeychellesStaticHolidays follows the same improved Markdown structure as the main class, maintaining consistency throughout the file.

holidays/countries/slovenia.py (2)

7-7: Consistent update to AUTHORS reference format

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency with the project-wide documentation migration.


22-28: Enhanced docstring with Markdown formatting

The docstring now includes a proper introductory line "Slovenia holidays." and follows Markdown link formatting with angle brackets and bullet points, improving readability.

holidays/countries/nicaragua.py (2)

7-7: Consistent update to AUTHORS reference format

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency across the codebase.


20-25: Improved docstring with Markdown formatting

Added an introductory line "Nicaragua holidays." and converted references to Markdown format with angle brackets and bullet points, enhancing documentation clarity.

holidays/countries/vanuatu.py (2)

7-7: Consistent update to AUTHORS reference format

The update from "AUTHORS file" to "AUTHORS.md file" aligns with the project-wide documentation standardization.


19-24: Improved docstring with Markdown formatting

The changes provide:

  1. A clear "Vanuatu holidays." introductory line
  2. Explicit "References:" section heading
  3. Properly formatted Markdown links with angle brackets and bullet points

These updates enhance readability and follow the new documentation standards.

holidays/countries/kuwait.py (3)

7-7: Correct update to AUTHORS.md reference

The update from "AUTHORS file" to "AUTHORS.md file" correctly reflects the new Markdown-based documentation structure.


21-26: Good docstring formatting improvement

The addition of "Kuwait holidays." as a clear class description and reformatting of references with asterisks and angle brackets enhances readability and follows Markdown conventions required by MkDocs.


37-40: Appropriate conversion to Google-style docstrings

The parameter documentation has been correctly converted from Sphinx-style (:param) to Google-style (Args:) format, which aligns with the PR objective of standardizing docstrings.

holidays/countries/bolivia.py (2)

7-7: Correct update to AUTHORS.md reference

The update from "AUTHORS file" to "AUTHORS.md file" correctly reflects the new Markdown-based documentation structure.


25-36: Well-formatted Markdown conversion

The class docstring has been properly updated with a clear "Bolivia holidays." description, and references have been converted to Markdown-style links with proper formatting. This enhances readability while maintaining all the original information.

holidays/countries/bulgaria.py (2)

7-7: Correct update to AUTHORS.md reference

The update from "AUTHORS file" to "AUTHORS.md file" correctly reflects the new Markdown-based documentation structure.


23-30: Good docstring structure and formatting

The addition of "Bulgaria holidays." as a clear class description and the introduction of a well-formatted References section enhances documentation clarity. The angle bracket formatting for URLs follows proper Markdown conventions.

holidays/countries/hongkong.py (2)

7-7: Correct update to AUTHORS.md reference

The update from "AUTHORS file" to "AUTHORS.md file" correctly reflects the new Markdown-based documentation structure.


54-67: Well-structured documentation formatting

The docstring has been properly updated with a clear "Hong Kong holidays." description. The References, Statutory Holidays, and General Holidays sections have been reformatted to use asterisks for bullet points, following Markdown conventions required by MkDocs.

holidays/countries/aruba.py (2)

7-7: Nice update to the AUTHORS reference.

The change from "AUTHORS file" to "AUTHORS.md file" is more precise and helpful for contributors looking to find the file.


22-31: Great clarity with the new URL formatting!

The bullet list with angle-bracketed URLs is much clearer and consistent. The addition of "Aruba holidays." as a title and the "References:" section header improves documentation readability.

holidays/calendars/balinese_saka.py (2)

7-7: Nice update to the AUTHORS reference.

The change from "AUTHORS file" to "AUTHORS.md file" is more precise and helpful for contributors looking to find the file.


109-110: Good improvement to reference formatting.

The bullet-point style (using asterisks) for reference URLs creates better visual separation and readability compared to the previous hyphenated format.

holidays/countries/samoa.py (3)

7-7: Nice update to the AUTHORS reference.

The change from "AUTHORS file" to "AUTHORS.md file" is more precise and helpful for contributors looking to find the file.


18-18: Good addition of descriptive title.

Adding "Samoa holidays." as a clear title for the class docstring improves immediate understanding of the class purpose.


21-24: Improved URL formatting enhances readability.

The bullet list with angle-bracketed URLs is much clearer and consistent, making the references section more scannable.

holidays/countries/india.py (3)

7-7: Nice update to the AUTHORS reference.

The change from "AUTHORS file" to "AUTHORS.md file" is more precise and helpful for contributors looking to find the file.


31-39: Great clarity with the new URL formatting!

The bullet list with angle-bracketed URLs is much clearer and consistent. The addition of "India holidays." as a title and the "References:" section header improves documentation readability.


153-156: Good switch to Google-style docstring format.

Changing from :param syntax to the Args: section follows Google-style docstring conventions, which aligns with the PR objectives for documentation standardization.

holidays/countries/lesotho.py (2)

7-7: AUTHORS reference updated to include file extension.

The reference to the AUTHORS file has been updated to include the .md extension, enhancing consistency with the Markdown-based documentation approach.


19-24: Docstring format improved and references standardized.

The country class docstring now consistently starts with "Lesotho holidays." and uses angle brackets for all reference links, which aligns with Markdown best practices.

holidays/countries/turkey.py (2)

7-7: AUTHORS reference updated to include file extension.

The reference to the AUTHORS file has been updated to include the .md extension, enhancing consistency with the Markdown-based documentation approach.


43-47: Parameter documentation updated to Google-style format.

The docstring parameter documentation has been effectively migrated from Sphinx's :param style to Google-style with "Args:" section, improving readability and consistency.

holidays/countries/greenland.py (2)

7-7: AUTHORS reference updated to include file extension.

The reference to the AUTHORS file has been updated to include the .md extension, enhancing consistency with the Markdown-based documentation approach.


21-26: Documentation formatting improved with mixed link styles.

The docstring is now cleaner with "Greenland holidays." as a title and bullet-point references. However, the references use both angle brackets and Markdown link syntax. Consider standardizing to one approach for all references across country files.

For consistency with other files, either:

- * <https://en.wikipedia.org/wiki/Public_holidays_in_Greenland>
- * [Greenlandic names source](https://nalunaarutit.gl/groenlandsk-lovgivning/2008/bkg-26-2008?sc_lang=kl-GL)
- * [Translation source](https://www.norden.org/en/info-norden/public-holidays-greenland)
+ * <https://en.wikipedia.org/wiki/Public_holidays_in_Greenland>
+ * <https://nalunaarutit.gl/groenlandsk-lovgivning/2008/bkg-26-2008?sc_lang=kl-GL> (Greenlandic names source)
+ * <https://www.norden.org/en/info-norden/public-holidays-greenland> (Translation source)

Or:

- * <https://en.wikipedia.org/wiki/Public_holidays_in_Greenland>
- * [Greenlandic names source](https://nalunaarutit.gl/groenlandsk-lovgivning/2008/bkg-26-2008?sc_lang=kl-GL)
- * [Translation source](https://www.norden.org/en/info-norden/public-holidays-greenland)
+ * [Wikipedia - Public holidays in Greenland](https://en.wikipedia.org/wiki/Public_holidays_in_Greenland)
+ * [Greenlandic names source](https://nalunaarutit.gl/groenlandsk-lovgivning/2008/bkg-26-2008?sc_lang=kl-GL)
+ * [Translation source](https://www.norden.org/en/info-norden/public-holidays-greenland)
holidays/countries/cyprus.py (2)

7-7: AUTHORS reference updated to include file extension.

The reference to the AUTHORS file has been updated to include the .md extension, enhancing consistency with the Markdown-based documentation approach.


22-26: Docstring format improved and references standardized.

The country class docstring now consistently starts with "Cyprus holidays." and uses angle brackets for all reference links, which aligns with Markdown best practices.

holidays/countries/andorra.py (2)

7-7: Good update to the AUTHORS reference

Consistent reference to AUTHORS.md file matches the updated documentation approach across the project.


18-22: Clean docstring formatting

The updated docstring format with a clear title and properly formatted URL references using angle brackets follows good Markdown documentation practices. This will render better in MkDocs compared to the previous format.

holidays/countries/dominican_republic.py (2)

7-7: Good update to the AUTHORS reference

Consistent reference to AUTHORS.md file aligns with the documentation migration strategy.


25-29: Well-structured docstring with improved formatting

The revised docstring now has a clear title, proper section formatting with "References:" label, and URLs enclosed in angle brackets for better Markdown rendering in MkDocs.

holidays/countries/armenia.py (2)

7-7: Good update to the AUTHORS reference

Updated AUTHORS reference to point to AUTHORS.md file matches the documentation migration strategy.


21-26: Improved docstring formatting for MkDocs compatibility

The updated docstring format with a clear title line and URLs in angle brackets will render better in the new MkDocs documentation system.

holidays/countries/mexico.py (2)

7-7: Good update to the AUTHORS reference

Consistent update to reference AUTHORS.md file aligns with the migration strategy.


20-27: Well-formatted docstring with proper Markdown structure

The docstring now follows good Markdown practices with a clear title, proper spacing, and URLs enclosed in angle brackets. This format will render well in MkDocs.

holidays/countries/ghana.py (3)

7-7: Good update to AUTHORS reference.

The reference to the "AUTHORS.md file" correctly reflects the new Markdown format, maintaining consistency with the PR's goal of transitioning from Sphinx to MkDocs documentation.


22-26: Well-structured documentation format.

The changes follow Markdown best practices:

  • Clear title "Ghana holidays."
  • Proper section heading with "References:"
  • URLs enclosed in angle brackets for proper rendering in Markdown
  • Good spacing that improves readability

This formatting will render well with MkDocs.


37-40: Good transition to Google-style docstrings.

The parameter documentation has been properly converted from Sphinx-style :param to Google-style Args: format, which aligns with the PR objective of standardizing docstrings.

holidays/countries/slovakia.py (2)

7-7: Good update to AUTHORS reference.

The reference to the "AUTHORS.md file" correctly reflects the new Markdown format, consistent with the documentation migration approach.


22-27: Well-structured documentation format.

The docstring has been properly formatted for Markdown:

  • Clear title "Slovakia holidays."
  • References section with URLs properly enclosed in angle brackets
  • Consistent bullet point formatting using asterisks

This will render correctly in MkDocs and improve documentation readability.

holidays/countries/monaco.py (2)

7-7: Good update to AUTHORS reference.

The reference has been properly updated to "AUTHORS.md file", maintaining consistency across the codebase.


21-25: Well-structured documentation format.

The docstring formatting follows Markdown conventions:

  • Added clear title "Monaco holidays."
  • Proper section heading with "References:"
  • URLs properly enclosed in angle brackets
  • Good use of spacing for readability

This formatting ensures proper rendering in MkDocs.

holidays/countries/belize.py (2)

7-7: Good update to AUTHORS reference.

The reference to the "AUTHORS.md file" correctly reflects the new Markdown format, consistent with the PR objective.


23-29: Well-structured documentation format.

The changes follow Markdown best practices:

  • Clear title "Belize holidays."
  • Properly formatted references section
  • URLs enclosed in angle brackets for proper Markdown rendering
  • Consistent bullet point formatting with asterisks

This formatting will display correctly in MkDocs and improves overall documentation consistency.

holidays/countries/maldives.py (3)

7-7: Documentation format update looks good

The update from "AUTHORS file" to "AUTHORS.md file" maintains consistency with the markdown-based documentation migration mentioned in the PR objectives.


19-24: Well-structured docstring format

The new format with a concise introduction "Maldives holidays." and references in angle brackets follows good documentation practices and is more readable. This change aligns with the PR objectives of enhancing documentation readability.


32-35: Good conversion to Google-style docstrings

The parameter documentation has been appropriately converted from Sphinx-style (:param) to Google-style (Args:), which matches the PR objective of standardizing docstring format.

holidays/calendars/chinese.py (1)

7-7: Consistent documentation update

The change from "AUTHORS file" to "AUTHORS.md file" correctly maintains consistency with the markdown-based documentation across the project.

holidays/countries/south_africa.py (2)

7-7: Documentation reference updated correctly

The update from "AUTHORS file" to "AUTHORS.md file" aligns with the project-wide documentation migration to markdown format.


19-25: Improved docstring structure

The docstring now has a clear title "South Africa holidays." and properly formatted references section with angle-bracketed URLs. This change improves readability and is consistent with the standardization of documentation formatting across the project.

holidays/countries/paraguay.py (2)

7-7: Documentation reference consistent with project standard

The change from "AUTHORS file" to "AUTHORS.md file" maintains consistency with the markdown documentation standards mentioned in the PR.


22-31: Good docstring formatting improvement

The docstring now starts with a clear "Paraguay holidays." introduction and maintains a consistent reference format. The mix of markdown-style links and angle-bracketed URLs improves readability while preserving the information.

holidays/countries/barbados.py (2)

7-7: Good update to AUTHORS.md reference.

The change from "AUTHORS file" to "AUTHORS.md file" improves clarity by specifying the exact filename.


24-33: Well-structured docstring formatting.

The updated docstring uses a clear Markdown format with:

  • A concise first line description
  • Proper spacing
  • Bulleted reference links with angle brackets
  • Markdown-style link for the Public Holidays Act

This aligns perfectly with the MkDocs migration objective.

holidays/countries/united_states_virgin_islands.py (2)

7-7: Good update to AUTHORS.md reference.

Consistently updating the file reference across the codebase.


18-22: Clean docstring conversion to Markdown format.

The docstring has been properly formatted for MkDocs:

  • Clear opening line with country name
  • Appropriate spacing
  • URL enclosed in angle brackets for proper rendering

This maintains the same information while improving readability.

holidays/countries/kyrgyzstan.py (4)

7-7: Consistent AUTHORS.md reference update.

The reference to AUTHORS.md is updated as in other files.


19-19: Concise first-line docstring description.

Simple and direct introduction follows the documentation standard.


22-22: Properly formatted reference link.

The URL is now correctly formatted with angle brackets for MkDocs.


29-33: Good conversion to Google-style docstring parameters.

The parameters section now uses the clearer "Args:" format with proper indentation and spacing, improving readability.

holidays/countries/australia.py (3)

7-7: Consistent AUTHORS.md reference update.

Maintaining documentation consistency across files.


29-30: Clean docstring introduction.

The simplified first line with proper spacing follows the documentation standards established across other country modules.


32-49: Well-formatted reference links.

The comprehensive reference section has been properly converted to a bulleted list with:

  • Consistent indentation
  • Proper URL formatting with angle brackets
  • Markdown-style links for legislation references

This improves consistency and readability in the MkDocs output.

holidays/countries/croatia.py (2)

7-7: Documentation reference updated appropriately.

The reference to AUTHORS has been correctly updated to AUTHORS.md in line with the documentation migration to Markdown format.


20-26: Well-structured documentation format.

The docstring has been appropriately reformatted with a clear title "Croatia holidays" and properly formatted Markdown references using angle brackets, which aligns with the MkDocs documentation style.

holidays/countries/greece.py (3)

7-7: Documentation reference updated appropriately.

The reference to AUTHORS has been correctly updated to AUTHORS.md in line with the documentation migration to Markdown format.


26-26: Concise and clear docstring title.

The updated docstring format provides a clear and concise title for the class, following good documentation practices.


29-30: Improved link formatting for references.

The references have been properly reformatted using Markdown-style links with angle brackets. The 2024 Labor Day transfer link now uses standard Markdown link syntax instead of backticks, which will render better in MkDocs.

holidays/countries/vatican_city.py (3)

7-7: Documentation reference updated appropriately.

The reference to AUTHORS has been correctly updated to AUTHORS.md in line with the documentation migration to Markdown format.


20-20: Clear docstring title added.

Adding a clear title "Vatican City holidays" improves documentation readability.


23-37: Well-formatted reference links.

The references and cross-check links have been properly reformatted using Markdown-style links with angle brackets and consistent bullet points using asterisks instead of hyphens. This format will render well in MkDocs.

holidays/countries/montenegro.py (4)

7-7: Documentation reference updated appropriately.

The reference to AUTHORS has been correctly updated to AUTHORS.md in line with the documentation migration to Markdown format.


37-38: Well-structured docstring with clear title.

The addition of "Montenegro holidays" as a clear title for the class improves documentation readability.


40-42: Improved link formatting for references.

The references have been properly reformatted using Markdown-style links with angle brackets, which will render correctly in MkDocs.


59-63: Improved parameter documentation format.

The parameter documentation has been converted to Google-style with an "Args:" section, which aligns with the PR objective of standardizing docstring formats. This improves readability and consistency.

holidays/countries/poland.py (2)

7-7: Documentation update looks good

Updated reference to the AUTHORS.md file is consistent with the PR's goal of migrating to Markdown formats.


21-26: Documentation formatting improvements are well-structured

The docstring now includes a clear introductory sentence and properly formatted Markdown-style bullet points for the references, which enhances readability. This aligns well with the MkDocs migration.

holidays/countries/chad.py (3)

7-7: Proper AUTHORS.md reference

Reference to AUTHORS.md file is consistent with the documentation migration goals.


27-31: Docstring formatting improved

The introduction and reference formatting now follow Markdown conventions, which works better with MkDocs.


41-44: Parameter documentation style updated correctly

Changing from :param style to Google-style Args: section improves documentation consistency and readability. This aligns with the PR objective of converting docstrings to Google-style.

holidays/countries/north_macedonia.py (3)

7-7: AUTHORS.md reference updated consistently

The update to reference AUTHORS.md matches the pattern applied across the codebase.


19-22: Well-structured docstring format

The introduction "North Macedonia holidays." followed by a clear "References" section with properly formatted links improves documentation readability and consistency.


29-32: Google-style parameter documentation implemented correctly

The Args: section with properly indented parameter descriptions follows Google docstring conventions, enhancing documentation clarity.

holidays/countries/france.py (2)

7-7: AUTHORS.md reference updated

Documentation reference to AUTHORS.md file is consistent with other changes throughout the codebase.


20-24: Docstring structure improved

The docstring has been updated to follow the same pattern as other country classes, with a concise introduction "France holidays." and properly formatted Markdown-style references. This enhances consistency across the codebase.

holidays/financial/brasil_bolsa_balcao.py (2)

7-7: Consistent AUTHORS reference update looks good

The update to reference "AUTHORS.md file" instead of "AUTHORS file" maintains consistency with the documentation migration goals.


20-29: Well-structured reference formatting

The improved bullet-point formatting with Markdown-style links enhances readability and is consistent with the MkDocs styling approach.

holidays/countries/burkina_faso.py (4)

7-7: Consistent AUTHORS reference update

The update to reference "AUTHORS.md file" aligns with the documentation standardization across the codebase.


20-20: Clear class description added

Adding "Burkina Faso holidays." provides an immediate understanding of the class purpose, improving documentation clarity.


23-23: Reference link formatting improvement

The angle bracket format for the reference link follows Markdown best practices and improves rendering in the MkDocs output.


34-37: Google-style docstring formatting

The parameter documentation has been properly reformatted to use "Args:" style, which aligns with the Google-style docstring format mentioned in the PR objectives.

holidays/countries/saint_lucia.py (3)

7-7: Consistent AUTHORS reference update

The update to reference "AUTHORS.md file" maintains documentation consistency across the codebase.


20-20: Clear class description added

Adding "Saint Lucia holidays." provides immediate context about the class purpose.


23-27: Improved reference formatting

The transition from hyphen bullets to asterisk format with angle brackets for URLs improves readability and aligns with Markdown best practices.

holidays/countries/congo.py (4)

7-7: Consistent AUTHORS reference update

The update to reference "AUTHORS.md file" maintains documentation consistency.


20-20: Clear class description added

Adding "Congo holidays." provides immediate context about the class's purpose.


23-24: Markdown-style links for better readability

The transition to Markdown-style links for law references improves documentation clarity and makes the references directly clickable in MkDocs output.


27-27: Consistent URL formatting

The angle bracket format for the cross-checked reference aligns with Markdown best practices and documentation standards.

holidays/financial/ice_futures_europe.py (2)

7-7: AUTHORS reference updated to markdown format.

The reference to the AUTHORS file has been updated to AUTHORS.md, which aligns with the Sphinx to MkDocs migration.


18-24: Documentation format standardized.

The docstring has been reformatted to follow a consistent pattern with:

  1. A clear descriptive line "ICE Futures Europe holidays."
  2. Properly formatted references with angle brackets

This standardization improves readability and aligns with MkDocs formatting expectations.

holidays/countries/bahamas.py (2)

7-7: AUTHORS reference updated to markdown format.

The reference to the AUTHORS file has been updated to AUTHORS.md, which aligns with the Sphinx to MkDocs migration.


26-38: Documentation format standardized.

The docstring has been reformatted to follow a consistent pattern with:

  1. A clear descriptive line "Bahamas holidays."
  2. Properly formatted references using asterisk bullets with angle brackets

This standardization improves readability and aligns with MkDocs formatting expectations.

holidays/countries/malawi.py (2)

7-7: AUTHORS reference updated to markdown format.

The reference to the AUTHORS file has been updated to AUTHORS.md, which aligns with the Sphinx to MkDocs migration.


22-27: Documentation format standardized.

The docstring has been reformatted to follow a consistent pattern with:

  1. A clear descriptive line "Malawi holidays."
  2. Properly formatted references using asterisk bullets with angle brackets

This standardization improves readability and aligns with MkDocs formatting expectations.

holidays/countries/portugal.py (2)

7-7: AUTHORS reference updated to markdown format.

The reference to the AUTHORS file has been updated to AUTHORS.md, which aligns with the Sphinx to MkDocs migration.


21-34: References section reformatted with mixed link styles.

The references section has been updated to use asterisk bullets instead of hyphens, which is consistent with the MkDocs migration. However, there's inconsistency in the link formatting - some use angle brackets while others use Markdown link syntax (square brackets with text).

Consider standardizing all links to use the same format for consistency. Either use angle brackets for all URLs or Markdown link syntax throughout.

holidays/countries/jordan.py (3)

7-7: Consistent documentation reference update.

The reference to AUTHORS file has been properly updated to AUTHORS.md file, maintaining consistency with the documentation migration to Markdown format.


21-25: Improved docstring structure and formatting.

The class docstring now starts with a clear "Jordan holidays." description and uses proper Markdown formatting for references with angle brackets. This enhances readability and follows modern documentation standards.


36-39: Improved parameter documentation style.

The change from :param to Args: follows Google-style docstrings, which renders better in MkDocs with mkdocstrings. The multi-line formatting also improves readability.

holidays/countries/el_salvador.py (1)

7-7: Consistent documentation reference update.

The reference to AUTHORS file has been properly updated to AUTHORS.md file, maintaining consistency with the documentation migration to Markdown format.

holidays/countries/nigeria.py (3)

7-7: Consistent documentation reference update.

The reference to AUTHORS file has been properly updated to AUTHORS.md file, maintaining consistency with the documentation migration to Markdown format.


26-29: Improved docstring structure with references section.

The docstring now includes a clear class description followed by a properly formatted References section with angle brackets for URLs. This follows good documentation practices and improves readability.


38-41: Improved parameter documentation style.

The change from :param to Args: follows Google-style docstrings, which renders better in MkDocs with mkdocstrings. The multi-line formatting also improves readability.

holidays/countries/mauritania.py (3)

7-7: Consistent documentation reference update.

The reference to AUTHORS file has been properly updated to AUTHORS.md file, maintaining consistency with the documentation migration to Markdown format.


19-23: Improved docstring structure and formatting.

The class docstring now starts with a clear "Mauritania holidays." description and uses proper Markdown formatting for references with angle brackets. This enhances readability and follows modern documentation standards.


31-34: Improved parameter documentation style.

The change from :param to Args: follows Google-style docstrings, which renders better in MkDocs with mkdocstrings. The multi-line formatting also improves readability.

holidays/countries/albania.py (3)

7-7: Consistent file reference update looks good.

Updated reference to AUTHORS.md file aligns with the repository's move to Markdown documentation.


30-35: Documentation standardization looks good.

The new docstring format with the "Albania holidays." introduction and properly formatted references with angle brackets for URLs improves readability and consistency.


52-55: Parameter documentation format improvement.

The conversion from Sphinx-style :param to Google-style Args: documentation follows modern Python documentation practices and improves readability.

holidays/countries/costa_rica.py (2)

7-7: Consistent file reference update looks good.

Updated reference to AUTHORS.md file aligns with the repository's move to Markdown documentation.


26-36: Documentation standardization looks good.

The new docstring format with the "Costa Rica holidays." introduction and properly formatted references improves readability and consistency across the codebase.

holidays/countries/germany.py (3)

7-7: Consistent file reference update looks good.

Updated reference to AUTHORS.md file aligns with the repository's move to Markdown documentation.


22-22: Documentation simplification looks good but consider preserving context.

The change from a more detailed description to "Germany holidays" aligns with the documentation standardization effort. However, you might want to retain the "official" designation in some form to preserve the context that these are government-recognized holidays.


243-248: Documentation standardization looks good.

The reformatted docstring with improved reference formatting using angle brackets for URLs enhances readability and consistency.

holidays/countries/romania.py (2)

7-7: Consistent file reference update looks good.

Updated reference to AUTHORS.md file aligns with the repository's move to Markdown documentation.


21-25: Documentation enhancement looks good.

The addition of "Romania holidays." and proper "References:" section with formatted URLs significantly improves the documentation structure and readability.

holidays/countries/panama.py (3)

7-7: File reference update looks good.

The update to reference AUTHORS.md instead of AUTHORS is consistent with the documentation migration to Markdown format.


22-23: Concise docstring introduction approved.

The simplified introduction "Panama holidays." follows good documentation practices with a clear, concise description.


25-30: References section properly formatted for Markdown.

The references section has been successfully converted to Markdown format, using asterisks for bullets and proper link formatting with angle brackets for plain URLs and Markdown-style links for titled references.

holidays/countries/ecuador.py (3)

7-7: File reference update looks good.

The update to reference AUTHORS.md instead of AUTHORS is consistent with the documentation migration to Markdown format.


27-28: Concise docstring introduction approved.

The simplified introduction "Ecuador holidays." follows good documentation practices with a clear, concise description.


30-31: References section properly formatted for Markdown.

The references section has been successfully converted to Markdown format, using asterisks for bullets and proper link formatting.

holidays/countries/san_marino.py (2)

7-7: File reference update looks good.

The update to reference AUTHORS.md instead of AUTHORS is consistent with the documentation migration to Markdown format.


18-19: Concise docstring introduction approved.

The simplified introduction "San Marino holidays." follows good documentation practices with a clear, concise description.

holidays/countries/gabon.py (3)

7-7: File reference update looks good.

The update to reference AUTHORS.md instead of AUTHORS is consistent with the documentation migration to Markdown format.


20-21: Concise docstring introduction approved.

The simplified introduction "Gabon holidays." follows good documentation practices with a clear, concise description.


35-39: Parameter documentation format improved.

The conversion from :param to Args: format follows Google-style docstrings, which is mentioned in the PR objectives. This format is more readable and compatible with MkDocs and mkdocstrings.

holidays/countries/iran.py (3)

7-7: Approved: Consistent update to AUTHORS reference

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation migration from Sphinx to MkDocs mentioned in the PR objectives.


36-43: Documentation format looks good

The updated class docstring with a concise introduction "Iran holidays." and the references section reformatted to use asterisks instead of hyphens improves readability while maintaining the same content.


56-59: Approved: Parameter documentation follows Google style

The conversion of parameter documentation from :param style to Args: style follows Google docstring standards, which aligns with the PR objective to standardize docstrings.

holidays/countries/saudi_arabia.py (3)

7-7: Approved: Consistent update to AUTHORS reference

The change from "AUTHORS file" to "AUTHORS.md file" maintains consistency with other files in the repository.


30-35: Documentation format looks good

The updated class docstring with a concise introduction "Saudi Arabia holidays." and the references section reformatted to use asterisks instead of hyphens improves readability.


50-53: Approved: Parameter documentation follows Google style

The conversion of parameter documentation from :param style to Args: style follows Google docstring standards, which aligns with the PR's migration goals.

holidays/countries/guatemala.py (3)

7-7: Approved: Consistent update to AUTHORS reference

The update to reference "AUTHORS.md file" maintains consistency across the codebase.


22-23: Documentation format looks good

The addition of a concise introduction "Guatemala holidays." improves clarity.


25-30: Approved: References and moving holidays formatting improved

The reformatting of references and moving holidays sections using asterisks and better link formatting improves readability while preserving the content.

holidays/countries/eswatini.py (2)

7-7: Approved: Consistent update to AUTHORS reference

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation standardization efforts.


21-25: Documentation format looks good

The updated class docstring with a clear introduction "Eswatini holidays." and properly formatted references using asterisks improves document structure and readability.

holidays/countries/brunei.py (3)

7-7: Good update to AUTHORS file reference.

Consistently updating references from "AUTHORS file" to "AUTHORS.md file" improves documentation clarity and maintains standardization across the codebase.


57-103: Well-structured documentation format.

The docstring reformatting follows good Markdown practices with:

  • Clear, concise title "Brunei holidays."
  • Properly formatted reference links using angle brackets
  • Consistent use of asterisks for bullet points instead of hyphens

This format works well with MkDocs and improves readability.


121-125: Good transition to Google-style docstrings.

Changed parameter documentation to follow the Google docstring style with "Args:" section, which is more readable and consistent with the documentation migration goals.

holidays/countries/haiti.py (2)

7-7: Correct AUTHORS.md file reference.

Consistent update to the file reference, maintaining standardization across the project.


21-26: Clean docstring formatting improvement.

The docstring has been well-formatted with:

  • Clear "Haiti holidays." title
  • Properly structured references section with angle-bracketed URLs
  • Consistent asterisk formatting for list items

This formatting enhances readability and works well with MkDocs.

holidays/countries/chile.py (2)

7-7: Consistent AUTHORS.md file reference.

The reference update aligns with the project-wide standardization effort.


30-59: Excellent reference formatting with mixed link styles.

The docstring uses a combination of:

  • Direct angle-bracketed URLs: <https://www.feriados.cl>
  • Markdown-style links: [Excellent history of Chile holidays](http://www.feriadoschilenos.cl)

This mixed approach enhances readability while preserving all reference information. Good job maintaining consistency with bullet points using asterisks.

holidays/countries/lithuania.py (2)

7-7: Standardized AUTHORS.md file reference.

Consistent update across the codebase.


20-25: Clean and minimal docstring format.

The docstring follows the same clean pattern as the other files:

  • Simple "Lithuania holidays." title line
  • Well-formatted references with angle brackets
  • Consistent asterisk usage for list items

The simplicity works well with the documentation migration to MkDocs.

holidays/countries/bosnia_and_herzegovina.py (4)

7-7: Update to AUTHORS.md reference looks good.

This change consistently updates the reference to point to the Markdown version of the AUTHORS file, aligning with the documentation migration.


45-51: Well-structured references section.

The reformatting of the references section using Markdown-style bullet points (with <link> syntax) improves readability and organization in the MkDocs output while maintaining accessibility of the source links.


54-56: Enhanced observed holiday rules list.

Converting the observed holiday rules into a clear bullet-point list greatly enhances the documentation's clarity. Consider a minor grammatical tweak, e.g., using "if a holiday falls on Sunday" for improved readability, though this is just a nitpick.


80-83: Good conversion to Google-style docstring format.

The parameter documentation has been nicely updated to use the "Args:" format, which is more consistent with Google-style docstrings and aligns well with the MkDocs documentation system.

holidays/countries/cambodia.py (5)

7-7: AUTHORS.md reference update is consistent.

This change maintains consistency across the codebase, updating the reference to the Markdown version of the AUTHORS file.


22-22: Concise class description.

The simplified class description follows modern documentation practices by being more direct, which works well with MkDocs' presentation style.


25-28: Well-formatted references section.

The conversion to a bulleted list for references improves readability and accessibility of the source links in the MkDocs output.


30-33: Improved checked sources format.

The bulleted list format for checked sources enhances documentation structure and readability.


36-40: Clearer limitations section.

The conversion to a bulleted format for the limitations section improves readability while preserving the important content about date ranges and limitations.

holidays/countries/argentina.py (4)

7-7: AUTHORS.md reference update maintains consistency.

The reference update aligns with the documentation migration pattern applied throughout the codebase.


26-26: Clear and concise class description.

The simplified description follows the pattern established across other country classes, improving consistency.


29-63: Excellent references section reorganization.

The extensive reformatting of the references section using proper Markdown bullet points and structured formatting significantly improves readability. The organization of references by category (laws, decrees, year-specific links) makes the documentation much more accessible.


65-69: Well-structured movable holidays laws section.

The reformatting improves clarity by using consistent bullet points and indentation for the hierarchy of information, making it easier to understand the holiday observation rules.

holidays/calendars/hebrew.py (1)

7-7: AUTHORS.md reference update is consistent with project-wide changes.

This single-line update maintains consistency with the documentation migration pattern applied throughout the codebase.

holidays/countries/philippines.py (3)

7-7: Great update to reference the AUTHORS.md file.

This change is consistent with the Markdown-based documentation approach, making the reference more clear for users visiting the GitHub repository where .md files are rendered properly.


36-54: Excellent docstring formatting improvements.

The conversion to bullet-point style with proper Markdown links enhances readability and will render well in MkDocs. The references are well-structured and comprehensive.


67-70: Good adoption of Google-style docstring format.

The "Args:" format is clearer and more consistent with modern Python documentation standards, making it easier for developers to understand parameter usage.

holidays/countries/malaysia.py (3)

7-7: Appropriate update to AUTHORS.md reference.

Consistent with the documentation standardization across the codebase.


66-83: Excellent comprehensive docstring addition.

The newly added documentation provides valuable context about Malaysia's holiday rules, including legal references and explanations of weekend variations by region. This significantly improves the usability of the class.


150-153: Good conversion to Google-style parameter documentation.

The Args section clearly explains the purpose of the islamic_show_estimated parameter in a consistent format.

holidays/countries/venezuela.py (2)

7-7: Correct update to AUTHORS.md reference.

This change aligns with the standardization across all files in the codebase.


20-29: Greatly improved reference documentation.

The enhanced docstring now includes multiple sources with proper dates and links, significantly improving the documentation quality and traceability of holiday information sources.

holidays/countries/morocco.py (3)

7-7: Consistent update to AUTHORS.md reference.

This change maintains uniformity across the codebase's documentation.


20-24: Well-formatted reference documentation.

The change from "Primary sources:" to "References:" and the formatting of URLs with angle brackets and bullet points improves the Markdown rendering and readability.


35-38: Good transition to Google-style docstring format.

The "Args:" format provides clear and consistent parameter documentation, enhancing code readability.

holidays/calendars/thai.py (1)

7-7: Update to AUTHORS reference looks good

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation migration to Markdown format. This maintains consistency across the codebase.

holidays/countries/ireland.py (2)

7-7: AUTHORS reference update is consistent

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation migration to Markdown format.


19-23: Docstring format improved for Markdown compatibility

The docstring has been properly reformatted to follow Markdown conventions with a clear introductory line and properly formatted references using angle brackets for URLs.

holidays/countries/vietnam.py (3)

7-7: AUTHORS reference update is consistent

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation migration to Markdown format.


45-53: Docstring format improved for Markdown compatibility

The docstring has been properly reformatted to follow Markdown conventions with a clear introductory line "Vietnam holidays." and properly formatted references using Markdown link syntax.


151-156: Static holidays class docstring properly formatted

The docstring for VietnamStaticHolidays has been properly reformatted to follow Markdown conventions with appropriate formatting for references.

holidays/countries/belgium.py (2)

7-7: AUTHORS reference update is consistent

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the documentation migration to Markdown format.


21-27: Docstring format improved for Markdown compatibility

The docstring has been properly reformatted to follow Markdown conventions with a clear introductory line "Belgium holidays." and properly formatted references using angle brackets for URLs.

holidays/countries/iceland.py (2)

7-7: Consistent file reference update.

The update from "AUTHORS file" to "AUTHORS.md file" properly reflects the migration to Markdown documentation format.


21-25: Documentation format improved for MkDocs compatibility.

The docstring formatting changes with the explicit "Iceland holidays." title and the conversion of references to use asterisks and angle brackets improve readability and align with Markdown documentation standards.

holidays/countries/united_states.py (2)

7-7: Consistent file reference update.

The update from "AUTHORS file" to "AUTHORS.md file" properly reflects the migration to Markdown documentation format.


35-84: Well-structured reference documentation.

The comprehensive reorganization of references with proper Markdown formatting improves readability significantly. The state-by-state holiday links are now clearly presented with state codes in square brackets for single links, while Indiana correctly uses a nested bullet format for its multiple references, as previously confirmed.

I'm drawing upon prior discussions where it was clarified that state abbreviations should be encapsulated in square brackets when they're hyperlinks, while states with multiple links like Indiana should use a nested bullet format.

holidays/countries/peru.py (2)

7-7: Consistent file reference update.

The update from "AUTHORS file" to "AUTHORS.md file" properly reflects the migration to Markdown documentation format.


20-24: Documentation format improved for MkDocs compatibility.

The docstring formatting changes with the explicit "Peru holidays." title and the conversion of references to use asterisks and angle brackets improve readability and align with Markdown documentation standards.

holidays/countries/saint_kitts_and_nevis.py (3)

7-7: Consistent file reference update.

The update from "AUTHORS file" to "AUTHORS.md file" properly reflects the migration to Markdown documentation format.


22-32: Documentation format improved for MkDocs compatibility.

The docstring formatting changes with the explicit "Saint Kitts and Nevis holidays." title and the conversion of references to use asterisks and angle brackets improve readability. The "Cross-Checked With" section is also properly formatted for Markdown.


125-141: Documentation format improved for StaticHolidays class.

The SaintKittsAndNevisStaticHolidays class docstring has been updated with a proper title and reference formatting consistent with the rest of the codebase, maintaining documentation consistency.

holidays/countries/spain.py (3)

7-7: Consistent reference to AUTHORS.md is a good improvement.

The update from referencing "AUTHORS file" to "AUTHORS.md file" is precise and matches the documentation migration objectives.


29-50: Docstring improvements look great.

The docstring has been well-structured with:

  • Concise title "Spain holidays."
  • Better formatted references with proper Markdown links
  • Extended holiday coverage from 2010-2023 to 2010-2025
  • Added proper links for 2024 and 2025 references

These changes align perfectly with the MkDocs migration goals.


82-85: Parameter documentation follows Google-style convention properly.

The conversion to Google-style docstrings with the "Args:" section is correctly implemented and improves readability.

holidays/countries/burundi.py (3)

7-7: Consistent reference to AUTHORS.md is a good improvement.

The update from referencing "AUTHORS file" to "AUTHORS.md file" maintains consistency across the codebase.


18-25: Docstring restructuring enhances readability.

The changes are well executed:

  • Simplified title to "Burundi holidays."
  • Changed "Primary sources" to "References"
  • Improved URL formatting with angle brackets for better Markdown compatibility

These changes follow the MkDocs migration standards while preserving the important note about Sunday holidays.


34-37: Parameter documentation follows Google-style convention properly.

The conversion to Google-style docstrings with the "Args:" section improves readability and maintains consistent documentation style across modules.

holidays/countries/moldova.py (2)

7-7: Consistent reference to AUTHORS.md is a good improvement.

The update from referencing "AUTHORS file" to "AUTHORS.md file" maintains consistency with other files in the codebase.


22-26: Docstring structure improved for MkDocs compatibility.

The changes follow the documentation migration goals:

  • Added clear title "Moldova holidays."
  • Added explicit "References:" section
  • Applied proper Markdown formatting with angle brackets for URLs

This enhancement makes the documentation more readable in the new MkDocs format.

holidays/countries/palau.py (3)

7-7: Consistent reference to AUTHORS.md is a good improvement.

The update from referencing "AUTHORS file" to "AUTHORS.md file" maintains consistency across the codebase.


20-26: Well-structured docstring for MkDocs compatibility.

The changes to the Palau class docstring:

  • Added clear title "Palau holidays."
  • Applied proper Markdown formatting with angle brackets for URLs
  • Maintained important context about holiday implementation decisions

These improvements enhance readability while preserving critical information.


109-114: PalauStaticHolidays docstring improved for consistency.

The docstring for the PalauStaticHolidays class has been properly updated:

  • Clear title "Palau special holidays."
  • Consistent "References:" section added
  • URLs formatted with angle brackets for Markdown compatibility

This maintains the documentation style consistency throughout the module.

holidays/countries/algeria.py (3)

7-7: Consistent reference to AUTHORS.md file improves clarity.

The update from "AUTHORS" to "AUTHORS.md file" provides a more precise reference to the contributors file, making it easier for developers to locate the information.


21-26: Documentation format enhanced for MkDocs compatibility.

The references section now uses asterisks for bullet points and angle brackets for URLs, which aligns with Markdown formatting conventions. This maintains readability while ensuring proper rendering in the new MkDocs documentation system.


37-40: Parameter documentation now follows Google style format.

Converting the parameter documentation to use "Args:" format improves consistency and readability, making it easier for developers to understand the function parameters.

holidays/countries/belarus.py (3)

7-7: Consistent reference to AUTHORS.md file improves clarity.

The update from "AUTHORS" to "AUTHORS.md file" provides a more precise reference to the contributors file, making it easier for developers to locate the information.


23-36: Improved Documentation Formatting in the Belarus Class Docstring

The updated docstring now clearly presents the reference URLs in a structured list with asterisks and angle brackets. This format enhances readability and consistency, aligning well with the broader documentation migration objectives.


148-152: Documentation format in BelarusStaticHolidays class standardized.

The docstring now follows the same formatting conventions as the main class, with clear Markdown-compatible syntax for the references section.

holidays/countries/georgia.py (3)

7-7: Consistent reference to AUTHORS.md file improves clarity.

The update from "AUTHORS" to "AUTHORS.md file" provides a more precise reference to the contributors file, making it easier for developers to locate the information.


23-28: Documentation format enhanced for MkDocs compatibility.

The references section now uses asterisks for bullet points and angle brackets for URLs, which aligns with Markdown formatting conventions. The single-line docstring introduction also follows best practices.


103-107: GeorgiaStaticHolidays docstring standardized for consistency.

The docstring format now matches the formatting pattern used throughout the codebase, improving overall documentation consistency.

holidays/countries/china.py (2)

7-7: Consistent reference to AUTHORS.md file improves clarity.

The update from "AUTHORS" to "AUTHORS.md file" provides a more precise reference to the contributors file, making it easier for developers to locate the information.


22-64: Extensive documentation formatting improvements enhance readability.

The comprehensive references section has been reformatted with consistent Markdown syntax, making it significantly more readable. The changes maintain content while structuring the numerous references in a more accessible format.

The "Checked With" and "Limitations" sections also follow this consistent approach, creating a cohesive documentation style throughout the file. This is particularly valuable given the extensive nature of the references in this file.

holidays/countries/cuba.py (2)

7-7: References to AUTHORS file standardized to AUTHORS.md

Consistently updated file reference from AUTHORS to AUTHORS.md, aligning with the documentation migration objectives.


20-49: Well-structured docstring reformatting

The docstring has been greatly improved with clear sections for References and holiday details. The hyperlinks are now properly formatted using angle brackets for Markdown compatibility, and the organization of information with nested bullet points enhances readability.

holidays/countries/azerbaijan.py (4)

7-7: References to AUTHORS file standardized to AUTHORS.md

Consistently updated file reference from AUTHORS to AUTHORS.md, aligning with the documentation migration objectives.


28-34: Improved docstring formatting for Markdown compatibility

Bullet points now use asterisks instead of hyphens, and URLs are properly enclosed in angle brackets for better rendering in MkDocs.


49-54: Converted parameter documentation to Args section

The parameter documentation has been reformatted from colon-style to a clearer "Args:" section with improved indentation, enhancing readability while maintaining the same information.


265-278: Standardized reference formatting in AzerbaijanStaticHolidays

References are now consistently formatted with angle brackets around URLs for proper Markdown linking, maintaining the same quality improvements seen throughout the file.

holidays/countries/timor_leste.py (3)

7-7: References to AUTHORS file standardized to AUTHORS.md

Consistently updated file reference from AUTHORS to AUTHORS.md, aligning with the documentation migration objectives.


43-43: Updated limitation statement for Islamic holidays

The limitation note has been updated to reflect that exact dates for Islamic holidays are now available for 2011-2025 instead of 2011-2023, keeping the documentation current.


57-61: Converted parameter documentation to Args section

The parameter documentation has been reformatted from colon-style to a clearer "Args:" section with improved indentation, enhancing readability while maintaining the same information.

holidays/countries/kenya.py (4)

7-7: References to AUTHORS file standardized to AUTHORS.md

Consistently updated file reference from AUTHORS to AUTHORS.md, aligning with the documentation migration objectives.


36-42: Enhanced class docstring with clear description

Added a concise description "Kenya holidays." and improved reference formatting with angle brackets around URLs for proper Markdown linking.


59-63: Converted parameter documentation to Args section

The parameter documentation has been reformatted from colon-style to a clearer "Args:" section with improved indentation, enhancing readability while maintaining the same information.


207-220: Improved KenyaStaticHolidays docstring

Added a clear description "Kenya special holidays." and standardized reference formatting with angle brackets around URLs for proper Markdown linking.

holidays/countries/singapore.py (3)

7-7: Consistent update of AUTHORS reference.

The reference to the AUTHORS file has been correctly updated to AUTHORS.md format, aligning with the documentation migration goals.


44-61: Well-structured docstring improvements.

The updated Singapore class docstring follows good documentation practices:

  • Clear "Singapore holidays" title
  • Well-organized references with markdown-style links
  • Clearly formatted limitations section using bullet points

These changes enhance readability while maintaining all the necessary information.


71-74: Good migration to Google-style docstring format.

The parameter documentation now properly uses the "Args:" style, which improves clarity and consistency across the codebase.

holidays/countries/ethiopia.py (4)

7-7: Consistent update of AUTHORS reference.

The reference to the AUTHORS file has been correctly updated to AUTHORS.md format, aligning with the documentation migration goals.


24-28: Clean docstring formatting.

The Ethiopia class docstring has been formatted with a clear title and consistent URL formatting in the reference section.


38-49: Excellent improvement to _is_leap_year docstring.

The expanded docstring for the _is_leap_year method is a significant improvement:

  • Clear explanation of how Ethiopian leap years relate to Gregorian calendar
  • Detailed explanation of how this affects holidays
  • Explicit return value documentation

This level of detail greatly helps readers understand the implementation.


55-58: Good migration to Google-style docstring format.

The parameter documentation now properly uses the "Args:" style, which improves clarity and consistency across the codebase.

holidays/countries/indonesia.py (4)

7-7: Consistent update of AUTHORS reference.

The reference to the AUTHORS file has been correctly updated to AUTHORS.md format, aligning with the documentation migration goals.


44-52: Well-structured docstring improvements.

The class docstring has been properly formatted with:

  • Clear "Indonesia holidays" title
  • Consistent URL references
  • Improved overall readability

This follows the documentation standards established across other files.


68-71: Good migration to Google-style docstring format.

The parameter documentation now properly uses the "Args:" style, which improves clarity and consistency across the codebase.


593-641: Comprehensive reference documentation.

The IndonesiaStaticHolidays class documentation has been well organized with:

  • Clear title "Indonesia special holidays"
  • Properly formatted references for both Election Days and Joint Holidays
  • Consistent URL styling

These updates significantly improve the documentation quality.

holidays/countries/italy.py (2)

7-7: Consistent update of AUTHORS reference.

The reference to the AUTHORS file has been correctly updated to AUTHORS.md format, aligning with the documentation migration goals.


19-23: Improved docstring with consistent formatting.

The Italy class docstring has been updated with:

  • Clear "Italy holidays" title
  • Consistent URL references using a mix of angle brackets and markdown-style links
  • Better overall structure

This matches the formatting style used in other country modules.

holidays/countries/japan.py (2)

7-7: Consistent documentation reference updated

The reference to the AUTHORS file has been updated to AUTHORS.md, maintaining consistency with the new markdown documentation format.


35-39: Well-structured docstring formatting

The docstring has been properly reformatted following Markdown conventions with:

  • Clear introductory statement "Japan holidays."
  • Consistent reference formatting with angle brackets for URLs
  • Proper bullet points using asterisks

This aligns well with the MkDocs migration goals.

holidays/countries/luxembourg.py (2)

7-7: Consistent documentation reference updated

The reference to the AUTHORS file has been updated to AUTHORS.md, maintaining consistency with the new markdown documentation format.


20-23: Improved docstring structure and formatting

The docstring has been expanded and properly formatted with:

  • Clear introductory statement "Luxembourg holidays."
  • Dedicated "References:" section
  • Proper URL formatting with angle brackets
  • Consistent bullet point style using asterisks

These changes improve readability and align with Markdown conventions for MkDocs.

holidays/countries/tonga.py (3)

7-7: Consistent documentation reference updated

The reference to the AUTHORS file has been updated to AUTHORS.md, maintaining consistency with the new markdown documentation format.


27-73: Comprehensive docstring formatting improvement

The extensive docstring has been well reformatted following Markdown conventions:

  • Clear introductory statement "Tonga holidays."
  • Properly formatted references with angle brackets and asterisks for bullet points
  • Improved formatting of checked sources with consistent styling
  • Better structured observance rules with proper whitespace and indentation

This improves readability while maintaining all the original information.


206-211: Consistent formatting of nested class docstring

The TongaStaticHolidays class docstring has been reformatted to match the parent class style:

  • Clear descriptive title "Tonga special holidays."
  • Proper references formatting with angle brackets and asterisks

This maintains documentation consistency throughout the file.

holidays/countries/dominica.py (3)

7-7: Consistent documentation reference updated

The reference to the AUTHORS file has been updated to AUTHORS.md, maintaining consistency with the new markdown documentation format.


19-32: Well-structured docstring with improved formatting

The docstring has been properly reformatted following Markdown conventions:

  • Clear introductory statement "Dominica holidays."
  • References section with consistent angle bracket URL formatting
  • Cross-checked sources with descriptive labels where appropriate
  • Maintained the explanatory text with proper spacing

These changes enhance readability while preserving the original content.


109-116: Consistent formatting in static holidays class docstring

The DominicaStaticHolidays class docstring has been updated to match the main class:

  • Added descriptive title "Dominica special holidays."
  • Consistent references section with proper URL formatting
  • Uniform bullet point style using asterisks

This maintains a consistent documentation style throughout the file.

holidays/countries/guernsey.py (4)

7-7: Updated author reference for consistency.

The authors reference now correctly points to AUTHORS.md file, which aligns with the migration to MkDocs and markdown documentation.


26-32: Good class documentation update.

The docstring now provides a concise opening statement "Guernsey holidays." and properly formats references using Markdown link syntax with angle brackets. This improves readability and is compatible with MkDocs rendering.


34-34: Consistent reference formatting.

The reference under "Checked with:" now uses the same angle bracket syntax, maintaining consistency throughout the documentation.


235-265: Well-structured static holidays documentation.

The GuernseyStaticHolidays class documentation now follows the same structure and formatting as the main class, with a clear opening statement and consistent reference formatting using angle brackets. This unified approach improves documentation readability.

holidays/countries/kazakhstan.py (4)

7-7: Updated author reference for consistency.

The authors reference now correctly points to AUTHORS.md file, which aligns with the migration to MkDocs and markdown documentation.


30-40: Improved class documentation formatting.

The docstring now provides a concise opening statement "Kazakhstan holidays." and properly formats references using Markdown link syntax with angle brackets. The Islamic holidays section is consistently formatted with the same pattern.


56-60: Google-style parameter documentation.

The parameter documentation has been updated from Sphinx-style :param to Google-style Args:, which is more compatible with MkDocs and improves readability. This change is consistent with the documentation migration goal.


174-226: Enhanced static holidays documentation.

The KazakhstanStaticHolidays class documentation now uses a consistent formatting approach with a clear opening statement and well-structured references using bullet points and angle brackets. The year-based references are organized clearly.

holidays/countries/colombia.py (2)

7-7: Updated author reference for consistency.

The authors reference now correctly points to AUTHORS.md file, which aligns with the migration to MkDocs and markdown documentation.


20-34: Significantly improved reference documentation.

The Colombia class docstring has been completely overhauled with:

  1. A clear opening statement "Colombia holidays."
  2. Well-structured references using Markdown link syntax and bullet points
  3. Consistent formatting for the calendar references from the 1980s

This makes the documentation much more readable and maintainable while preserving all the original reference information.

holidays/countries/jersey.py (3)

7-7: Updated author reference for consistency.

The authors reference now correctly points to AUTHORS.md file, which aligns with the migration to MkDocs and markdown documentation.


28-40: Well-formatted class documentation.

The Jersey class docstring now features:

  1. A concise opening statement "Jersey holidays."
  2. References formatted consistently with either angle brackets or markdown-style links
  3. Bullet points using asterisks for better readability

This maintains consistency with the documentation style established in other files.


162-181: Consistently formatted static holidays documentation.

The JerseyStaticHolidays class documentation now follows the same pattern as other classes with a clear opening statement and consistently formatted references using angle brackets and bullet points.

holidays/countries/serbia.py (3)

7-7: Nicely updated authorship reference.

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the Markdown documentation standards being implemented in this migration.


21-21: Good use of concise documentation intro.

The new docstring format with "Serbia holidays." as the opening line provides a clear and immediate understanding of the class purpose.


24-24: Well-formatted reference link.

The updated reference format using angle brackets for the URL follows proper Markdown link formatting, which will render correctly in MkDocs.

holidays/countries/guam.py (2)

7-7: Consistent authorship reference update.

The change from "AUTHORS file" to "AUTHORS.md file" maintains consistency with other files in this migration.


18-22: Well-structured docstring with clear formatting.

The revised docstring now follows a consistent pattern with other country modules:

  1. Starts with a concise title "Guam holidays."
  2. Provides additional context about Guam's status
  3. Uses proper Markdown formatting for the reference link

This improvement enhances readability and maintains consistency across the documentation.

holidays/countries/jamaica.py (2)

7-7: Consistent authorship reference update.

The change from "AUTHORS file" to "AUTHORS.md file" aligns with the project-wide standardization.


23-27: Well-organized docstring with proper reference formatting.

The updated docstring follows the new standard format:

  1. Clear title "Jamaica holidays."
  2. Dedicated "References:" section
  3. Properly formatted URLs with angle brackets

This consistent structure improves documentation readability and will render nicely in MkDocs.

holidays/countries/norway.py (4)

7-7: Consistent authorship reference update.

The change from "AUTHORS file" to "AUTHORS.md file" maintains documentation consistency.


21-33: Well-structured docstring with improved organization.

The docstring has been significantly improved:

  1. Concise title "Norway holidays."
  2. Properly formatted references with angle brackets
  3. Better organization of notes about Sunday holidays

This makes the documentation more scannable and consistent with other country modules.


39-39: Added helpful type annotation.

Adding the : bool type annotation to the include_sundays parameter improves code quality by making the expected type explicit. This helps with IDE autocompletion and type checking.


41-43: Improved parameter documentation style.

Changing from :param style to "Args:" style for parameter documentation is consistent with Google-style docstrings mentioned in the PR description. This format will work well with mkdocstrings for API documentation generation.

holidays/countries/hungary.py (3)

7-7: Updated AUTHORS reference to include file extension.

The reference to the AUTHORS file has been correctly updated to "AUTHORS.md file" to match the new Markdown format.


21-26: Documentation improved with Markdown-style formatting.

The docstring has been reformatted to use proper Markdown formatting with a clear introduction line followed by a structured References section using angle brackets for URLs.


117-134: References section reformatted with consistent Markdown style.

The references in the HungaryStaticHolidays class docstring have been converted to a more readable format with proper Markdown link syntax. The formatting now provides a cleaner reference list with better visual structure.

holidays/countries/tanzania.py (4)

7-7: Updated AUTHORS reference to include file extension.

The reference to the AUTHORS file has been correctly updated to "AUTHORS.md file" to match the new Markdown format.


33-42: References section reformatted with proper Markdown style.

The references section has been converted from a hyphenated list to a proper Markdown list using asterisks, with better URL formatting for improved readability.


45-50: "Checked With" section uniformly formatted with asterisks.

The section now uses consistent Markdown bullet points with asterisks instead of hyphens, improving readability and aligning with Markdown best practices.


71-74: Docstring format updated to Google style.

The parameter documentation has been converted from Sphinx-style :param notation to Google-style documentation using the "Args:" section, which aligns with the PR objective of standardizing docstring formats.

holidays/countries/thailand.py (6)

7-7: Updated AUTHORS reference to include file extension.

The reference to the AUTHORS file has been correctly updated to "AUTHORS.md file" to match the new Markdown format.


48-88: References section reformatted with proper Markdown style.

The extensive list of references has been converted from hyphenated items to properly formatted Markdown bullet points with asterisks, improving readability and consistency.


90-132: Supporting documentation sections standardized with Markdown formatting.

The "Checked with:", "In Lieus:", and "Certain holidays references:" sections have been reformatted with consistent bullet point styling using asterisks, improving readability and navigation.


149-173: Added proper Markdown admonitions for notes and info.

The sections about public holiday handling have been restructured using MkDocs-compatible admonition syntax (!!! info and !!! note), which will render as visually distinct callout boxes in the generated documentation.


175-181: Limitations section reformatted with consistent Markdown style.

The limitations section has been updated to use asterisks for bullet points, maintaining consistent formatting throughout the document.


975-975: Fixed inconsistent bullet point format.

The bullet point has been changed from a hyphen - to an asterisk *, making it consistent with the rest of the documentation.

holidays/countries/ukraine.py (3)

7-7: Updated AUTHORS reference to include file extension.

The reference to the AUTHORS file has been correctly updated to "AUTHORS.md file" to match the new Markdown format.


25-30: Docstring reformatted with cleaner Markdown style.

The Ukraine class docstring has been simplified and reformatted to use proper Markdown link formatting, making it more readable and consistent with the documentation style used throughout the project.


169-218: References section thoroughly reformatted with consistent Markdown style.

The extensive list of references for substituted and special holidays has been converted from hyphenated items to properly formatted Markdown bullet points with asterisks. The section headers have also been improved for better organization.

holidays/countries/papua_new_guinea.py (3)

7-7: Consistent authorship reference update

The authorship reference now points to "AUTHORS.md file" instead of "AUTHORS file", which aligns with the project's migration to Markdown documentation.


21-35: Well-structured docstring improvements

The docstring formatting changes enhance readability by:

  1. Using a clear, concise introduction statement
  2. Converting the references to proper Markdown-style links with angle brackets
  3. Maintaining consistent bullet list formatting

These changes align well with the MkDocs migration goals.


135-146: Improved documentation clarity and completeness

Good improvements to the PapuaNewGuineaStaticHolidays class documentation:

  1. Fixed the class description to be more precise
  2. Converted references to Markdown-formatted links
  3. Added valuable context about the Port Moresby-specific APEC Holiday

The added note about Nov 15, 2018 being an APEC Holiday specific to Port Moresby provides important contextual information that was missing before.

holidays/countries/sri_lanka.py (4)

7-7: Consistent authorship reference update

The authorship reference now points to "AUTHORS.md file" instead of "AUTHORS file", which aligns with the project's migration to Markdown documentation.


52-76: Improved reference formatting for better readability

The docstring references have been reformatted from a hyphenated list to a bullet-point format with properly formatted Markdown links. This enhances readability and follows Markdown best practices.


93-97: Google-style docstring parameter format

The parameter description format has been updated to use the "Args:" section format, which aligns with Google docstring style conventions. This is consistent with the PR objective to convert docstrings to Google-style.


376-396: Fixed typo and improved reference formatting

The changes include:

  1. Fixed typo: "holdays" → "holidays" in the class description
  2. Reformatted references to use Markdown bullet points and proper URL formatting

This improves documentation accuracy and readability.

holidays/countries/israel.py (2)

7-7: Consistent authorship reference update

The authorship reference now points to "AUTHORS.md file" instead of "AUTHORS file", which aligns with the project's migration to Markdown documentation.


31-36: Improved docstring formatting

The docstring has been updated with:

  1. Cleaner opening format for the class description
  2. Properly formatted Markdown-style links with angle brackets
  3. Consistent bullet point formatting for references

These changes enhance readability and conform to Markdown best practices.

holidays/countries/laos.py (4)

7-7: Consistent authorship reference update

The authorship reference now points to "AUTHORS.md file" instead of "AUTHORS file", which aligns with the project's migration to Markdown documentation.


23-37: Well-structured documentation with improved formatting

The docstring has been significantly improved with:

  1. Cleaner introduction statement
  2. References section formatted as proper Markdown bullet points with angle brackets for URLs
  3. "Checked with" section converted to a bulleted list for better readability

This enhances the documentation's clarity and maintainability.


38-47: Better formatted notes and improved readability

The note regarding public holidays falling on weekends has been reformatted using the MkDocs note admonition syntax (!!! note). This makes the important information stand out better while maintaining good readability in both rendered documentation and source code.


49-52: Consistent list formatting

The limitations section has been reformatted to use consistent bullet point styling and indentation, improving the docstring's overall readability and structure.

holidays/countries/sweden.py (3)

7-7: AUTHORS file reference updated to AUTHORS.md

The file reference has been updated to reflect the new Markdown format, maintaining consistency with the documentation migration.


21-36: Improved docstring formatting with Markdown conventions

The class docstring has been reformatted to follow Markdown conventions, with asterisks for bullet points and improved heading structure. The title now matches the class name format used throughout the codebase ("Sweden holidays").


42-47: Enhanced parameter documentation with type hints

The __init__ method now includes a type hint for the include_sundays parameter and uses Google-style docstring format with the Args: section. This improves both code clarity and documentation readability.

holidays/countries/south_korea.py (3)

7-7: AUTHORS file reference updated to AUTHORS.md

The file reference has been updated to reflect the new Markdown format, maintaining consistency with the documentation migration.


54-67: Docstring Formatting Update in SouthKorea Class

The updated docstring now uses Markdown-style asterisks for bullet points and proper Markdown links. This change improves clarity and aligns with the overall documentation migration strategy.


201-213: Enhanced Docstring in SouthKoreaStaticHolidays Class

This docstring has been reformatted to adopt Markdown conventions, including a numbered list and the use of asterisks for bullet points. The extra asterisks at the end of some reference lines follow a consistent pattern for styling.

holidays/countries/united_arab_emirates.py (4)

7-7: AUTHORS file reference updated to AUTHORS.md

The file reference has been updated to reflect the new Markdown format, maintaining consistency with the documentation migration.


38-57: Well-structured docstring with improved reference formatting

The class documentation has been transformed into a more readable format with:

  • Clear title matching the class name
  • Year-based organization of references
  • Proper URL formatting with angle brackets for better visibility in rendered documentation

This structure will render well in MkDocs and improves source readability.


71-75: Converted parameter documentation to Google style

The parameter documentation has been updated from Sphinx-style (:param) to Google-style (Args:) format, bringing it in line with the project's new documentation standards.


201-216: Improved special holidays documentation structure

The special holidays docstring now features:

  • Clear title
  • Properly structured lists for better readability
  • Consistent use of angle brackets for URLs
  • Better organization of reference years

This formatting will display correctly in MkDocs and improves the documentation clarity.

holidays/holiday_base.py (13)

7-7: AUTHORS file reference updated to AUTHORS.md

The file reference has been updated to reflect the new Markdown format, maintaining consistency with the documentation migration.


59-85: Comprehensive docstring formatting improvements

The class docstring has been thoroughly updated with:

  • Consistent code block formatting using backticks for inline code
  • Markdown-style bullet points with asterisks
  • Improved explanation of date handling
  • Better visual spacing and organization

These changes significantly improve readability while maintaining the original information.


83-99: Improved Docstring Format for the HolidayBase Class.

The updated introductory docstring now employs Markdown-style formatting and lists the acceptable date types clearly. This change enhances readability in MkDocs.


175-183: Enhanced code example formatting

The code example has been reformatted with proper indentation and Markdown-style code blocks. This ensures the example renders correctly in MkDocs and maintains consistent spacing.


207-209: Updated documentation reference links

Function and class references have been updated from Sphinx-style markup (:func:, :class:) to Markdown-style links, which is consistent with the migration to MkDocs.


269-302: Comprehensive parameter documentation in Google style

The __init__ method documentation has been significantly improved with:

  • Clearly structured Args: section for all parameters
  • Consistent indentation for better readability
  • Added Returns: section that was previously missing
  • Maintained deprecation warnings for prov and state parameters

This thorough documentation provides clear guidance for all initialization options.


747-751: Added meaningful return value documentation

The get_subdivision_aliases() method now includes proper return value documentation that clearly explains what the method returns, replacing the previous zero-width space character.


925-934: Complete documentation added for append method

The append() method documentation has been significantly improved with:

  • Clear explanation of its relationship to the update() method
  • Properly formatted Args: section that explains all accepted types
  • Detailed explanation of how each argument type is handled

This replaces the previous placeholder documentation that had only zero-width space characters.


942-963: Enhanced get method documentation

The get() method documentation now features:

  • Comprehensive explanation of return values for different scenarios
  • Well-structured Args: section with clear parameter descriptions
  • Complete Returns: section that was previously empty
  • Detailed list of accepted input types

This provides users with clear guidance on how to use this fundamental method.


1046-1062: Complete docstring for get_closest_holiday

The documentation for get_closest_holiday() now includes:

  • Thorough explanation of the method's behavior in different scenarios
  • Clear parameter descriptions for both target_date and direction
  • Proper return value documentation that explains the tuple format

This addresses previous review comments about incomplete documentation.


1085-1099: Comprehensive documentation for get_nth_working_day

The get_nth_working_day() method now has complete documentation with:

  • Clear explanation of the method's purpose and behavior
  • Well-described parameters explaining how positive/negative values affect direction
  • Proper return value documentation

This addresses previous review comments about incomplete documentation for this method.


1109-1123: Complete return documentation in get_working_days_count

The get_working_days_count() method documentation now includes:

  • Clear description of what the method returns
  • Well-explained parameters
  • Useful context about the closed interval behavior

This addresses previous review comments about missing return documentation.


1132-1140: Complete documentation for is_working_day

The is_working_day() method now has proper documentation with:

  • Clear description of its purpose
  • Well-explained parameter
  • Complete return value documentation that explains the boolean result

This addresses previous review comments about incomplete documentation for this method.

holidays/countries/united_states_minor_outlying_islands.py (2)

7-7: Good update to AUTHORS reference.

The change from AUTHORS to AUTHORS.md reflects the documentation migration from Sphinx to MkDocs and follows proper markdown convention. This consistency helps developers locate the file more easily.


18-22: Improved docstring formatting.

The previous single-line comment has been replaced with a properly structured docstring that clearly identifies:

  1. The class purpose (holidays for United States Minor Outlying Islands)
  2. Its relationship to US subdivisions
  3. A properly formatted markdown link to the ISO reference

This follows the Google-style docstring format mentioned in the PR objectives and improves readability.

@arkid15r
Copy link
Copy Markdown
Collaborator

@Roshan-1024 thanks for a great contribution! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate project documantation to mkdocs

4 participants