refactor(*): rewrite to TypeScript and graphql-pokemon API

We're going TypeScript in here awe yeah!

test: add remaining test cases for dexintent
test: refactor test setup
feat: add move intent
feat: add item and ability intents

BREAKING CHANGE: TypeScript port means the old code is fully reworked and is not compatible with any old code

Signed-off-by: Jeroen Claassens <support@favware.tech>

.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = false
+charset = utf-8
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true

.eslintignore

@@ -1 +1,3 @@
-functions/dexa/data/*.js
+legacy/
+**/dist/*.js
+**/docs/

.eslintrc

@@ -0,0 +1,15 @@
+{
+  "extends": [
+    "@favware"
+  ],
+  "rules": {
+    "new-cap": "off",
+    "object-curly-newline": "off",
+    "no-invalid-this": "off",
+    "no-useless-escape": "off",
+    "jest/valid-expect-in-promise": "off"
+  },
+  "parserOptions": {
+    "createDefaultProgram": true
+  }
+}

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# Favna
+/src/**/* @favna
+/scripts/**/* @favna

.github/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 support@favware.tech. 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/

.github/CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing
+
+**The issue tracker is only for bug reports and enhancement suggestions. If you have a question, please ask it in the [Discord server](https://favware.tech/redirect/server) instead of opening an issue – you will get redirected there anyway.**
+
+If you wish to contribute to the Favware project's codebase or documentation, feel free to fork the repository and submit a
+pull request. We use ESLint to enforce a consistent coding style, any PR that does not follow the linting rules will not be
+merged until the formatting is resolved.
+
+## Setup
+To get ready to work on the codebase, please do the following:
+
+1. Fork & clone the repository, and make sure you're on the **master** branch
+2. Run `yarn install`
+3. Code your heart out!
+4. Ensure your changes compile (`yarn build`) and run by testing them using GraphQL Playground.
+ - You can start compiling in watch mode with `yarn watch`
+ - You can start a dev server with `yarn dev`
+5. If you have any substantial code changes make sure these are covered in unit tests
+6. Run `yarn lint && yarn test` to run ESLint and ensure all tests pass
+7. Submit a pull request

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+github: Favna
+patreon: Favna
+custom: https://donatebot.io/checkout/512303595966824458

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report incorrect or unexpected behaviour of this library
+title: 'Fix(): '
+assignees: ''
+
+---
+
+<!--
+If you need help with the library installation or usage, please go to the Discord server instead:
+  https://favware.tech/redirect/server
+This issue tracker is only for bug reports and enhancement suggestions.
+You likely won't receive any basic help here.
+-->
+
+**Please describe the problem you are having in as much detail as possible:**
+
+
+**Include a reproducible code sample here, if possible:**
+```js
+
+// Place your code here
+
+```
+
+**Further details:**
+- version:
+- Node.js version:
+- Operating system:
+- Priority this issue should have – please be realistic and elaborate if possible:
+
+<!--
+If this applies to you, please check the respective checkbox: [ ] becomes [x].
+You don't have to modify the text to suit your particular situation – if you want to
+elaborate, please do so in the description.
+While it's not a requirement to test your issue on the master branch, it would make fixing
+the problem a lot easier for us, so please do so if possible.
+-->
+
+- [ ] I have also tested the issue on latest master, commit hash:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Request a feature for the library
+title: 'Feat(): '
+assignees: ''
+
+---
+
+<!--
+If you need help with the library installation or usage, please go to the Discord server instead:
+  https://favware.tech/redirect/server
+This issue tracker is only for bug reports and enhancement suggestions.
+You likely won't receive any basic help here.
+-->
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the ideal solution**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question---general-support-request.md

@@ -0,0 +1,15 @@
+---
+name: Question / General support request
+about: Ask for help in Discord instead - https://favware.tech/redirect/server
+title: ''
+assignees: ''
+
+---
+
+Seriously, we only use this issue tracker for bugs in the library itself and feature requests for it.
+We don't typically answer questions or help with support issues here.
+Instead, please ask in one of the support channels in our Discord server:
+
+https://favware.tech/redirect/server
+
+Any issues that don't directly involve a bug in the library or a feature request will likely be closed and redirected to the Discord server.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1 @@
+**Please describe the changes this PR makes and why it should be merged:**