cleanup

Author: gunnarmein-ts

Algebra.js

@@ -0,0 +1,5 @@
+*version 0.8.0*
+- Order of arguments changed for *defint* in `nerdamer.convertToLaTeX`
+- `nerdamer.toRPN` not returns array of tokens. Token class can be found in Parser.classes
+- The `Operator` class was removed. A simple `object` can be passed to method
+- nerdamer.setOperator and nerdamer.getOperators have been deprecated. Use `core.PARSER.setOperator` instead.

BREAKING_CHANGES.md

@@ -0,0 +1,10 @@
+cff-version: 1.2.0
+title: "Nerdamer"
+message: "If you use this software, please cite it as below.""
+version: 1.1.3
+date-released: 2021-11-01
+url: "https://nerdamer.com"
+license: "MIT License"
+authors:
+  - family-names: Donk
+    given-names: Martin

CITATION.cff

@@ -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 martin.r.donk@gmail.com. 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/

CODE_OF_CONDUCT.md

@@ -0,0 +1,14 @@
+# Contributing
+Thank you for your interest in contributing to the project. You can submit a pull request at any time with your changes. Please make sure to target the `dev` branch when submitting and not the `master` branch.
+
+Any contribution is welcomed granted the following are performed:
+
+ 1. Make sure that all unit tests pass. The unit tests are written for **jasmine**. To run the tests, first make sure you install [node.js](https://nodejs.org/en/download/) and [jasmine](https://www.npmjs.com/package/jasmine). Follow the link to install nodejs. You can install jasmine by running `npm install -g jasmine`. Once that's complete you can navigate to your project folder root and type `jasmine`. Please be aware that at the moment, some tests will fail for versions of node.js > 10.xx due to rounding errors.
+ 2. Make sure that there's isn't already an existing solution on the `dev` branch.
+
+Feel free to reach out if you need any guidance navigating the code. Seriously. A slow response doesn't mean you're being ignored but simply that life is in progress. You will however get a response at some point.
+
+# Issues
+Please do report any issues you find. If you don't report it, then there's no way of knowing the issue exists in the first place. There are existing issues labeled "Pending issues with xxx". These are just to keep related issues organized. So for instance if you're having a problem with `simplify` you can just add your issue under "Pending issues with simplify". Be sure to mention @jiggzson when reporting.
+
+Give as much information as possible about your issue and try to give it a meaningful subject line. If possible, add an example of what works and what doesn't. If you've already done some debugging, feel free to share since it may help speed up the fix.