chore: set prettier prose wrap to always for md

Author: jmcdo29

.prettierrc

@@ -7,10 +7,9 @@
     {
       "files": "*.md",
       "options": {
-        "printWidth": 70,
         "useTabs": false,
         "trailingComma": "none",
-        "proseWrap": "never"
+        "proseWrap": "always"
       }
     }
   ]

CODE_OF_CONDUCT.md

@@ -2,9 +2,14 @@
 
 ## 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, religion, or sexual identity and orientation.
+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, 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.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and
+healthy community.
 
 ## Our Standards
 
@@ -13,67 +18,96 @@ Examples of behavior that contributes to a positive environment for our communit
 - 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
+- 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
+- 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 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.
+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.
+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.
+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.
+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:
+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.
+**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.
+**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.
+**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.
+**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.
+**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.
+**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.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
 
 [homepage]: https://www.contributor-covenant.org
 
-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.
+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.

CONTRIBUTING.md

@@ -2,11 +2,15 @@
 
 ## Reporting Issues
 
-If you find an issue, please [report it here](https://github.com/jmcdo29/nest-commander/issues/new/choose). Follow the issue template and please fill out the information. Especially if it is a bug, please provide a [minimum reproduction repository](https://minimum-reproduction.wtf).
+If you find an issue, please
+[report it here](https://github.com/jmcdo29/nest-commander/issues/new/choose). Follow the issue
+template and please fill out the information. Especially if it is a bug, please provide a
+[minimum reproduction repository](https://minimum-reproduction.wtf).
 
 ## Pre-Requisites
 
-- [pnpm installed](https://pnpm.io) (you can try using `yarn` or `npm`, but sometimes they don't play nicely with the pnpm workspace)
+- [pnpm installed](https://pnpm.io) (you can try using `yarn` or `npm`, but sometimes they don't
+  play nicely with the pnpm workspace)
 - [Basic knowledge of Nx](https://nx.dev)
 
 ### Getting Started
@@ -22,26 +26,50 @@ And now you should be good to go
 
 ### Project Structure
 
-`nest-commander` uses an [`nx`](https://nx.dev) workspace for development. This means that the packages can be found under `packages/` and each package has its own set of commands that can be found in the [`workspace.json`](./workspace.json) file. All of the docs for `nest-commander` can be found at `apps/docs/docs` and are all markdown files [thanks to docusaurus](https://docusaurus.io/). All integration tests can be found at `integration/`
+`nest-commander` uses an [`nx`](https://nx.dev) workspace for development. This means that the
+packages can be found under `packages/` and each package has its own set of commands that can be
+found in the [`workspace.json`](./workspace.json) file. All of the docs for `nest-commander` can be
+found at `apps/docs/docs` and are all markdown files [thanks to docusaurus](https://docusaurus.io/).
+All integration tests can be found at `integration/`
 
 ### Making changes
 
-Generally changes and improvements are appreciated, especially if they make logic less complex or they end up causing [codebeat](https://codebeat.co/) report a major (greater than .2) loss in code GPA. Other than that, follow the lint rules set up in the project, and make sure the git hooks run before [opening a Pull Request](https://github.com/jmcdo29/nest-commander/compare). Also, make sure if it's a new feature or a bug fix that a test is added to the integration tests. Lastly, please resolve any merge conflicts by [rebasing](https://git-scm.com/book/en/v2/Git-Branching-Rebasing). The easiest way to go about this is to use `git pull --rebase upstream main` where `upstream` is a remote set to `https://github.com/jmcdo29/nest-commander.git` or `[email protected]:jmcdo29/nest-commander.git` depending on if you use HTTPS or SSH with your git client.
+Generally changes and improvements are appreciated, especially if they make logic less complex or
+they end up causing [codebeat](https://codebeat.co/) report a major (greater than .2) loss in code
+GPA. Other than that, follow the lint rules set up in the project, and make sure the git hooks run
+before [opening a Pull Request](https://github.com/jmcdo29/nest-commander/compare). Also, make sure
+if it's a new feature or a bug fix that a test is added to the integration tests. Lastly, please
+resolve any merge conflicts by [rebasing](https://git-scm.com/book/en/v2/Git-Branching-Rebasing).
+The easiest way to go about this is to use `git pull --rebase upstream main` where `upstream` is a
+remote set to `https://github.com/jmcdo29/nest-commander.git` or
+`[email protected]:jmcdo29/nest-commander.git` depending on if you use HTTPS or SSH with your git
+client.
 
 #### Adding a Changeset
 
-If you're making a change that you'd like to be published, please consider running `pnpm changeset` and following the wizard for setting up a changeset for the change. When this gets merged into `main`, the GitHub Actions will end up opening a new PR afterwards for updating the version and publishing to npm. [If you're interested in how, there's a blog post about it here](https://dev.to/jmcdo29/automating-your-package-deployment-in-an-nx-monorepo-with-changeset-4em8). The wizard is pretty straight forward, I do ask that you try to follow [semver](https://semver.org/) as much as possible and don't make major changes unless absolutely necessary.
+If you're making a change that you'd like to be published, please consider running `pnpm changeset`
+and following the wizard for setting up a changeset for the change. When this gets merged into
+`main`, the GitHub Actions will end up opening a new PR afterwards for updating the version and
+publishing to npm.
+[If you're interested in how, there's a blog post about it here](https://dev.to/jmcdo29/automating-your-package-deployment-in-an-nx-monorepo-with-changeset-4em8).
+The wizard is pretty straight forward, I do ask that you try to follow [semver](https://semver.org/)
+as much as possible and don't make major changes unless absolutely necessary.
 
 ### Building just one project
 
-If you need to just build a single project, you can use `pnpm nx build <project-name>`. If you want to build everything that has been affected you can instead use `pnpm build` which will use `nx affected:build` instead.
+If you need to just build a single project, you can use `pnpm nx build <project-name>`. If you want
+to build everything that has been affected you can instead use `pnpm build` which will use
+`nx affected:build` instead.
 
 ### Testing just one suite
 
-To run the tests, you can use `pnpm e2e` or `pnpm nx e2e integration`, this will run all of the integration tests, it shouldn't take more than 15 seconds. If it does, there's most likely an `exit` call that was mocked and not restored. Ping me on discord and we can try to find it.
+To run the tests, you can use `pnpm e2e` or `pnpm nx e2e integration`, this will run all of the
+integration tests, it shouldn't take more than 15 seconds. If it does, there's most likely an `exit`
+call that was mocked and not restored. Ping me on discord and we can try to find it.
 
 If you need to just run one of the test suites you can use `pnpm e2e -- --testFile=<fileName>`.
 
 ## Keeping in touch
 
-You can get a hold of me (Jay) by [emailing me](mailto:[email protected]) or by contacting me on [the Nest Discord](https://discord.gg/6byqVsXzaF) (there's a channel dedicated to `nest-commander`)
+You can get a hold of me (Jay) by [emailing me](mailto:[email protected]) or by contacting me on
+[the Nest Discord](https://discord.gg/6byqVsXzaF) (there's a channel dedicated to `nest-commander`)