https://github.com/intermine/bluegenes-go-term-visualizer
https://github.com/intermine/bluegenes-go-term-visualizer
bluegenes-tool
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/intermine/bluegenes-go-term-visualizer
- Owner: intermine
- License: mit
- Created: 2019-06-12T14:20:11.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2021-02-18T16:27:46.000Z (over 4 years ago)
- Last Synced: 2025-05-06T14:08:46.459Z (about 1 month ago)
- Topics: bluegenes-tool
- Language: JavaScript
- Homepage:
- Size: 682 KB
- Stars: 1
- Watchers: 7
- Forks: 7
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# BlueGenes GO-term Visualizer
BlueGenes GO-term Visualizer is a tool made for [BlueGenes](http://bluegenes.apps.intermine.org) following BlueGenes Tool API.
Visualize gene ontology terms by their amount of matches for items in a list. Allows you to filter and adjust the enrichment results.
## Licence
MIT
### To set up locally for development
1. Clone the repo
2. `cd bluegenes-GO-term-visualizer` and then `npm install` to install dependencies.
All of the editable source files for css and js are in `src`. To bundle for prod, run the following commands:
#### CSS
Assuming [less](http://lesscss.org/) is installed globally:
```
npm run less
```
#### JS
Assuming [webpack](https://webpack.js.org/) is installed globally:
##### Single build:
```
npm run build
```
##### Applied Coding practices / ESLint Rules:
- _indent_: use __tab (2 space tab)__ instead of spaces to not get an error.
- _linebreak-style_: use __\n__ for a newline, if you're on windows, configure it in your editor settings.
- _quotes_: use __single quote__ instead of double quote.
- _semi_: use _semi colon_ at end of each statement / expression / function definition.
- _comma-dangle_: do not use dangling commas i.e. extra comma at the end of object values, function args, etc.). More about this [here](https://eslint.org/docs/rules/comma-dangle).
- More pre-configured rules from __eslint:recommended__ you must follow to not get errors [here](https://eslint.org/docs/rules/).
##### Developing:
To serve your code at [localhost:3456](http://localhost:3456) and rebuild it every time it changes, run:
```bash
npm run dev
```