Merge pull request #1872 from TruckMap/chore/camera

Refactor TS integration and convert Camera to TS

Author: naftalibeder

.eslintignore

@@ -1 +1,3 @@
-/plugin/build
+/plugin/build
+/example
+/lib

.github/pull_request_template.md

@@ -20,7 +20,7 @@ Added `your feature` that allows ...
 - [ ] I have tested this on a device/simulator for each compatible OS
 - [ ] I updated the documentation with running `yarn generate` in the root folder
 - [ ] I mentioned this change in `CHANGELOG.md`
-- [ ] I updated the typings files (`index.d.ts`)
+- [ ] I updated the typings files (`definitions.d.ts`)
 - [ ] I added/ updated a sample (`/example`)
 
 ## Screenshot OR Video

.gitignore

@@ -58,6 +58,10 @@ package-lock.json
 yarn.lock
 /example/yarn.lock
 
+# Compiled
+lib
+*.tgz
+
 # Expo
 .expo
 

CONTRIBUTING.md

@@ -1,30 +1,33 @@
 # Contributing
 
 ## Setup for creating pull requests
+
 - Fork this project
 - In your fork, create a branch, for example: `fix/camera-update`
 - Add your changes
 - Push and open a PR with your branch
 
 ## Testing my changes
+
 The metro bundler under `/example` is set up to use the libraries files under root.  
 Which means, when you change something within `javascript/components/UserLocation.js`  
 it will be reflected in any scene in example that uses that component.
 
 ## Best practices for PR's
+
 - If you add a feature, make sure you add it to the documentation
-- If you add an objective-c or java method, make sure you update the declaration file: `index.d.ts`.
+- If you add an objective-c or java method, make sure you update the declaration file: `definitions.d.ts`.
 - Make sure to use small concise commits
 - Use meaningful commit messages
 - Make sure to update/ add new tests for your changes
 - If you add a new feature make sure to add a scene in `/example` for others to see/ test it
 
 ## Documentation
+
 Documentation is generated from code blocks and comments.  
 It will be auto-generated when you commit changes.  
 If any changes are generated from your edits, the changed files will need to be added using `git add` before attempting the commit again.  
-To manually generate the changes, run `npm run generate`.  
+To manually generate the changes, run `npm run generate`.
 
 Notice, that changing the documentation in the individual <COMPONENT>.md within `/docs` will not suffice.  
 The correct way is the above described
-