npm install keen-explorer --save
;const myExplorer =container: '#keen-explorer-html-element' // querySelectorpersistence: true // optional: ability to save queries etckeenAnalysisOptions:// configuration for KeenAnalysis//projectId: 'PROJECT_ID'masterKey: 'MASTER_KEY'keenDatavizOptions:// OPTIONAL configuration for KeenDataviz//;
Install from CDN
<!-- Dependencies --><!-- Explorer Assets -->
Get your project ID & API keys
If you haven’t done so already, login to Keen IO to create a project for your app. You'll need a Keen IO account to create a project. The Project ID and API Keys are available on the Project Overview page. You will need these for the next steps.
Custom builds of the Explorer
- Clone our repo
git clone https://github.com/keen/explorer.git
- Configure the Keen.js client in the demo file at test/demo/demo-config.js with your project ID and Keen IO API keys.
- Install the dependencies with
- Run the development script with
npm run start.
- You can now view the demo locally at
http://localhost:8080/or your specified port.
Building the project:
The project is built with Webpack.
npm run buildfrom the root directory of the project to build ALL files, including the minified versions for production use.
Run Unit Tests
npm run testto run all the tests. Currently there are only unit tests.
Is this open source Keen Explorer different than the one on keen.io? Nope! We have recently moved all our development on the Keen Explorer to this open source version.
I have questions about using the project! Where/who do I ask? If you have any questions about using this project, Explorer feel free to contact us anytime at firstname.lastname@example.org.
To contribute to this project:
- Fork the repo.
- Submit a Pull Request with test coverage.
- Follow our PR template, which includes the following sections:
## What does this PR do? How does it affect users?## How should this be tested?Step through the code line by line. Things to keep in mind as you review:- Are there any edge cases not covered by this code?- Does this code follow conventions (naming, formatting, modularization, etc) where applicable?Fetch the branch and/or deploy to staging to test the following:- [ ] Does the code compile without warnings (check shell, console)?- [ ] Do all tests pass?- [ ] Does the UI, pixel by pixel, look exactly as expected (check various screen sizes, including mobile)?- [ ] If the feature makes requests from the browser, inspect them in the Web Inspector. Do they look as expected (parameters, headers, etc)?- [ ] If the feature sends data to Keen, is the data visible in the project if you run an extraction (include link to collection/query)?- [ ] If the feature saves data to a database, can you confirm the data is indeed created in the database?## Related tickets?
Screenshots encouraged! Would an animated GIF be more informative than a screenshot? Then we recommend Recordit.
Tech used in this project
These are the major technologies used in the project.