Update fork

.codeclimate.yml

@@ -0,0 +1,39 @@
+---
+version: "2"
+plugins:
+  duplication:
+    enabled: true
+    config:
+      languages:
+      - php
+  fixme:
+    enabled: true
+  markdownlint:
+    enabled: true
+  phpcodesniffer:
+    enabled: true
+    config:
+      file_extensions: "php"
+      standard: "WordPress-Docs,WordPress-Extra"
+  phpmd:
+    enabled: true
+    checks:
+      Controversial/CamelCaseMethodName:
+        enabled: false
+      Controversial/CamelCaseParameterName:
+        enabled: false
+      Controversial/CamelCasePropertyName:
+        enabled: false
+      Controversial/CamelCaseVariableName:
+        enabled: false
+      CleanCode/ElseExpression:
+        enabled: false
+  shellcheck:
+    enabled: true
+exclude_patterns:
+  - "**.dist"
+  - "**.lock"
+  - "**.json"
+  - "**.txt"
+  - "tests/*"
+  - "vendor/**"

.editorconfig

@@ -0,0 +1,21 @@
+# This file is for unifying the coding style for different editors and IDEs
+# editorconfig.org
+
+# WordPress Coding Standards
+# https://make.wordpress.org/core/handbook/coding-standards/
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = tab
+
+[{.jshintrc,*.json,*.yml}]
+indent_style = space
+indent_size = 2
+
+[{*.txt,wp-config-sample.php}]
+end_of_line = crlf

.gitattributes

@@ -0,0 +1,25 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files that will always be normalized and converted
+# to native line endings on checkout.
+.editorconfig   text
+.gitattributes  text
+.gitignore      text
+*.json          text
+*.md            text
+*.txt           text
+*.xml           text
+*.yml           text
+
+# Declare files that will always have LF line endings on checkout.
+*.php text eol=lf
+*.sh  text eol=lf
+
+# Exclude from export.
+.*                  export-ignore
+bin                 export-ignore
+tests               export-ignore
+*.dist              export-ignore
+CODE_OF_CONDUCT.md  export-ignore
+composer.*          export-ignore

.github/CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Want to contribute?
+
+Did you know that you could be instrumental in making the WP Bootstrap NavWalker more robust? If you use and love it, why not contribute to the project?
+
+## Contributing for Everyone!
+
+Whether you can barely recognize a filter (or don’t know what that means) or you’ve already authored your own plugins, there are ways for you to pitch in.
+
+### Create Bug Reports
+
+If you find a bug, just [file a GitHub issue](https://github.com/wp-bootstrap/wp-bootstrap-navwalker/issues), that’s all. If you want to prefix the title with a “Question:”, “Bug:”, or the general area of the application, that would be helpful, but by no means mandatory. If you have write access, add the appropriate labels.
+
+If you’re filing a bug, specific steps to reproduce are helpful. Please include the URL of the page that has the bug, along with what you expected to see and what happened instead. 
+
+### Write and submit a patch
+
+If you'd like to fix a bug, you can submit a Pull Request. 
+
+#### Where to get started?
+
+If you'd like to contribute but don't know where to get started, you can take a look at existing issues:
+
+- ["Good First Bug"](https://github.com/wp-bootstrap/wp-bootstrap-navwalker/labels/%5BTYPE%5D%20GOOD%20FIRST%20BUG) issues are a good entry point to get familiar with the codebase.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,15 @@
+<!-- Thanks for contributing to WP Bootstrap NavWalker! Pick a clear title and proceed. -->
+
+#### Steps to reproduce the issue:
+
+#### What I expected:
+
+#### What happened instead:
+
+<!--
+PLEASE NOTE
+- These comments won't show up when you submit the issue.
+- Everything is optional, but try to add as many details as possible.
+- If requesting a new feature, explain why you'd like to see it added.
+- This issue tracker is not for support.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,12 @@
+Fixes #
+
+#### Changes proposed in this Pull Request:
+
+*
+
+#### Testing instructions:
+
+*
+
+<!-- Add the following only if this is meant to be in changelog -->
+#### Proposed changelog entry for your changes:

.gitignore

@@ -0,0 +1,2 @@
+/vendor/
+/phpcs.xml

.travis.yml

@@ -0,0 +1,75 @@
+language: php
+
+os:
+  - linux
+
+dist: bionic
+
+php:
+  - 7.4
+  - 7.3
+  - 7.2
+  - 7.1
+  - nightly
+
+env:
+  - WP_VERSION=latest WP_MULTISITE=0 PHPUNIT_VERSION="^5.7"
+  - WP_VERSION=latest WP_MULTISITE=1 PHPUNIT_VERSION="^5.7"
+
+services:
+  - mysql
+
+jobs:
+  include:
+    - php: 7.0
+      dist: xenial
+      env:
+        - WP_VERSION=latest WP_MULTISITE=0 PHPUNIT_VERSION="^5.7"
+    - php: 7.0
+      dist: xenial
+      env:
+        - WP_VERSION=latest WP_MULTISITE=1 PHPUNIT_VERSION="^5.7"
+    - php: 5.6
+      dist: xenial
+      env:
+        - WP_VERSION=latest WP_MULTISITE=0 PHPUNIT_VERSION="^5.7"
+    - php: 5.6
+      dist: xenial
+      env:
+        - WP_VERSION=latest WP_MULTISITE=1 PHPUNIT_VERSION="^5.7"
+    - name: "Coding Standars"
+      php: 7.4
+      install:
+        - composer require --dev wp-coding-standards/wpcs dealerdirect/phpcodesniffer-composer-installer
+        # Counter wp-enforcer
+        - rm -f ./phpcs.xml
+      script:
+        - vendor/bin/phpcs
+    - name: "Static Analysis"
+      php: 7.4
+      install:
+        - composer require --dev szepeviktor/phpstan-wordpress
+      script:
+        - vendor/bin/phpstan analyze
+  allow_failures:
+    - php: nightly
+
+branches:
+  only:
+    - master
+
+cache:
+  directories:
+    - "${HOME}/.composer/cache"
+
+install:
+  - bin/install-wp-tests.sh wordpress_test root "" localhost "${WP_VERSION}"
+  - composer global require --dev "phpunit/phpunit=${PHPUNIT_VERSION}"
+
+script:
+  - "${HOME}/.composer/vendor/bin/phpunit"
+
+notifications:
+  email:
+    on_success: never
+    on_failure: change

CHANGELOG.md

@@ -0,0 +1,90 @@
+#CHANGELOG
+
+## [4.3.0]
+- Added an `aria-current` item.
+- Added `.nav-item` for the `<li>` and `.nav-link` for the `<a>` in fallback function.
+- Some escape improvements.
+- Don't pass `$attributes` to element closing function as it's ignored anyway.
+
+## [4.2.0]
+- Fix typo in function name 'seporate'->'separate' (private function, no need to add back-compat).
+
+## [4.1.0]
+- Prevent error `trying to get property of non-object` when no menu is set to a location using the walker.
+- Add `$depth` as 4th parameter passed to `nav_menu_link_attributes`.
+- Add support for `dropdown-item-text` linkmod type.
+## [4.0.3]
+- Drop composer class autoload statement.
+
+## [4.0.2]
+- Fix dropdown opener having empty string for href value.
+- More accurate regex matching of icon and linkmod classnames.
+- Changed composer package type to `library` from `wordpress-plugin` again.
+- Tests: Add unit tests for the function that separates classnames for the walker.
+- Fix case sensitive matching to now match mixes of upper and lower case.
+
+## [4.0.1]
+- Fix untranslated string in fallback (this was lost in transition between v3 and v4, fixed again).
+
+## [4.0.0]
+- Added a prefix on @since tags to highlight when they refer to WP core instead of this class.
+- Rework of `start_lvl()` and `start_el()` based on latest `Walker_Nav_Menu` Class from WP core.
+	- Whitespace preservation method improvements.
+	- Added `nav_menu_item_args` filter and `nav_menu_item_title` brought in at WP 4.4.0
+	- Use `the_title` filter prior to `nav_menu_item_title`.
+- Added a labelled-by attribute to dropdowns for accessibility.
+- Links inside dropdown have `.dropdown-item` instead of `.nav-link`.
+- Remove `<span class="carat">` after parent dropdown items.
+- Support `echo` arg in fallback menu. props: @toddlevy
+- Add `.active` to parent when a child is current page. props: @zyberspace
+- Fix to correct output of dropdown atts and styles when depth passed to wp_nav_menu is <= 1. props: @chrisgeary92
+- Move icon output to a local var instead of modifying and clearing a global object.
+- Reassign filtered classes back to $classes array so that updated classes can be accessed later if needed. props: @lf-jeremy
+- Update to work with Bootstrap v4.
+	- Added `.nav-item` and `.nav-link` to `<li>` and `<a>` respectively.
+- Dropped support for using title attribute to add link modifiers and icons.
+- Added support for link modifiers and icons through WP Menu Builder 'classes' input.
+	- Icon support is for Font Awesome 4/5 and Glyphicons icons.
+- Added unit tests for the `fallback` method.
+- Added code to handle icon-only menus.
+
+## [3.0.0]
+
+- Fix untranslated string in fallback.
+- Instruct screenreaders to ignore icons when present.
+- Added basic unit tests and travis config.
+- Swapped to IF statements with curly braces.
+- Adds `$depth` arg for nav_menu_css_class filter.
+- Fix sanitization function used for class output in fallback.
+- Changed composer package type to `library` from `wordpress-plugin`.
+
+## [2.0.5] - 2016-011-15
+
+- Fixed all reported issues by WP Enforcer.
+- Fixed several Code Climate issues.
+
+## [2.0.4]
+
+- Updated fallback function to accept args array from `wp_nav_menu`.
+
+## [2.0.3]
+
+- Included a fallback function that adds a link to the WordPress menu manager if no menu has been assigned to the theme location.
+
+## [2.0.2]
+
+- Small tweak to ensure carets are only displayed on top level dropdowns.
+
+## [2.0.1]
+
+- Added missing active class to active menu items.
+
+## [2.0.0]
+
+- Class was completly re-written using the latest Wordpress 3.6 walker class.
+- Now full supports Bootstrap 3.0+
+- Tested with wp_debug & the Theme Check plugin.
+
+
+---
+<small>All notable changes to this project will be documented in this file. Please read [Keep a Change Log](http://keepachangelog.com) for more information. This project adheres to [Semantic Versioning](http://semver.org).</small>

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/