v0.7.3 (#415)

* chore: update heading format of news

* Increment version number to 0.7.3

* chore: use_tidy_description()

* chore: use_tidy_coc()

* chore: use_github_links()

* chore: use_roxygen_md(); roxygen2md::roxygen2md()

* chore: air format .

* chore: use_cran_comments()

* chore: revdepcheck::cloud_check()

* chore: update CRAN comments

Author: gadenbuie

.Rbuildignore

@@ -7,3 +7,5 @@
 ^appveyor\.yml$
 ^\.github$
 ^LICENSE\.md$
+^cran-comments\.md$
+^revdep$

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,126 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at [email protected]. 
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][https://github.com/mozilla/inclusion].
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.
+
+[homepage]: https://www.contributor-covenant.org

DESCRIPTION

@@ -1,24 +1,28 @@
 Package: shinydashboard
 Title: Create Dashboards with 'Shiny'
-Version: 0.7.2.9000
+Version: 0.7.3
 Authors@R: c(
-    person("Winston", "Chang", role = c("aut", "cre"), email = "[email protected]"),
+    person("Winston", "Chang", , "[email protected]", role = c("aut", "cre")),
     person("Barbara", "Borges Ribeiro", role = "aut"),
-    person(family = "Posit Software, PBC", role = "cph"),
-    person(family = "Almasaeed Studio", role = c("ctb", "cph"), comment = "AdminLTE theme for Bootstrap"),
-    person(family = "Adobe Systems Incorporated", role = c("ctb", "cph"), comment = "Source Sans Pro font")
-    )
-Description: Create dashboards with 'Shiny'. This package provides
-    a theme on top of 'Shiny', making it easy to create attractive dashboards.
-URL: http://rstudio.github.io/shinydashboard/
+    person(, "Posit Software, PBC", role = "cph"),
+    person(, "Almasaeed Studio", role = c("ctb", "cph"),
+           comment = "AdminLTE theme for Bootstrap"),
+    person(, "Adobe Systems Incorporated", role = c("ctb", "cph"),
+           comment = "Source Sans Pro font")
+  )
+Description: Create dashboards with 'Shiny'. This package provides a theme
+    on top of 'Shiny', making it easy to create attractive dashboards.
+License: MIT + file LICENSE
+URL: https://rstudio.github.io/shinydashboard/,
+    https://github.com/rstudio/shinydashboard
+BugReports: https://github.com/rstudio/shinydashboard/issues
 Depends:
     R (>= 3.0)
-License: MIT + file LICENSE
 Imports:
-    utils,
-    shiny (>= 1.0.0),
     htmltools (>= 0.2.6),
-    promises
-BugReports: https://github.com/rstudio/shinydashboard
-RoxygenNote: 7.3.2
+    promises,
+    shiny (>= 1.0.0),
+    utils
 Encoding: UTF-8
+Roxygen: list(markdown = TRUE)
+RoxygenNote: 7.3.2

NEWS.md

@@ -1,18 +1,16 @@
-# shinydashboard (development version)
+# shinydashboard 0.7.3
 
 ### Bug fixes
 
-* Fixed [#397](https://github.com/rstudio/shinydashboard/issues/397): `updateTabItems()` is now a run-time alias of `shiny::updateTabsetPanel()`. ([#398](https://github.com/rstudio/shinydashboard/pull/398))
+* Fixed [#397](https://github.com/rstudio/shinydashboard/issues/397): `updateTabItems()` is now a run-time alias of `shiny::updateTabsetPanel()`. ([#398](https://github.com/rstudio/shinydashboard/pull/370))
 
-shinydashboard 0.7.2
-====================
+# shinydashboard 0.7.2
 
 ### Bug fixes
 
 * Fixed [#369](https://github.com/rstudio/shinydashboard/issues/369): `renderMenu()` did not work correctly when shinydashboard was built against shiny 1.6.0 (and older) but used with shiny 1.7.0 (and higher). ([#370](https://github.com/rstudio/shinydashboard/pull/370))
 
-shinydashboard 0.7.1
-====================
+# shinydashboard 0.7.1
 
 ## Full changelog
 
@@ -24,8 +22,7 @@ shinydashboard 0.7.1
 
 * Fixed [#297](https://github.com/rstudio/shinydashboard/issues/297): recent versions of Shiny caused the sidebar toggle icon to not render because FontAwesome was upgraded in Shiny. ([#299](https://github.com/rstudio/shinydashboard/pull/299))
 
-shinydashboard 0.7.0
-====================
+# shinydashboard 0.7.0
 
 ## Full changelog
 
@@ -43,8 +40,7 @@ shinydashboard 0.7.0
 
 * Fixed [#229](https://github.com/rstudio/shinydashboard/issues/229): only run `ensureActivatedTab()` after `renderMenu()` is called *_if_* the `el` in question has class `"sidebar-menu"`. Since this function is used for both `dropdownMenuOutput` and `sidebarMenuOutput`, we have to make sure that `ensureActivatedTab()` is only called if it's the latter case (otherwise, you get unexpected tab redirections when updating a dropdown menu). ([#233](https://github.com/rstudio/shinydashboard/pull/233))
 
-shinydashboard 0.6.1
-====================
+# shinydashboard 0.6.1
 
 This is a hotfix release of shinydashboard, meant to fix a few edge cases that have surfaced since the last release.
 
@@ -54,8 +50,7 @@ This is a hotfix release of shinydashboard, meant to fix a few edge cases that h
 
 * Fixed [#217](https://github.com/rstudio/shinydashboard/issues/217): correct `input$sidebarCollapsed` value for edge cases by attaching the change event to the end of the sidebar CSS transitions (instead of when the toggle button is clicked). Also make sure that `input$sidebarCollapsed` is set to `FALSE` when the app starts up with the sidebar already collapsed. ([#222](https://github.com/rstudio/shinydashboard/pull/222))
 
-shinydashboard 0.6.0
-====================
+# shinydashboard 0.6.0
 
 This release of shinydashboard was aimed at both fixing bugs and also bringing the package up to speed with users' requests and Shiny itself (especially fully bringing [bookmarkable state](https://shiny.rstudio.com/articles/bookmarking-state.html) to shinydashboard's sidebar). In addition to the changes listed below, we also added a [new "Behavior" section to the shinydashboard website](https://rstudio.github.io/shinydashboard/behavior.html) to explain this release's two biggest new features.
 
@@ -105,22 +100,19 @@ This release of shinydashboard was aimed at both fixing bugs and also bringing t
 
 * Updated to AdminLTE 2.3.11. ([#181](https://github.com/rstudio/shinydashboard/pull/181))
 
-shinydashboard 0.5.3
-=========================
+# shinydashboard 0.5.3
 
 * Fixed ([#160](https://github.com/rstudio/shinydashboard/issues/160): Using a dynamically-created `sidebarMenu` without an `id` argument would cause the app to not start, when used with Shiny 0.14.
 
-shinydashboard 0.5.2
-====================
+# shinydashboard 0.5.2
 
 * Added ability to bookmark and restore tabs, when used with Shiny 0.14 and above. ([#152](https://github.com/rstudio/shinydashboard/issues/152), [#157](https://github.com/rstudio/shinydashboard/pull/157))
 
 * Fixed issue with R CMD check and Shiny version 0.14.
 
 * Updated to AdminLTE 2.3.2 (1ee281b).
 
-shinydashboard 0.5.1
-====================
+# shinydashboard 0.5.1
 
 * Logout panels from Shiny Server Pro were previously not visible, but now they are.
 
@@ -132,8 +124,7 @@ shinydashboard 0.5.1
 
 * `radioButtons` did not wrap, but now they do. (#60)
 
-shinydashboard 0.5.0
-====================
+# shinydashboard 0.5.0
 
 * Updated to AdminLTE 2.1.2 (406de4e). Please note that some CSS selectors have changed, so if you are using custom CSS, it may require modification. The documentation at http://rstudio.github.io/shinydashboard/appearance.html has some updated examples.