1
1
mirror of https://github.com/aelve/guide.git synced 2024-11-23 21:13:07 +03:00
A workspace for research teams
Go to file
Gigiman 3d8fee8c5c
Category description add edit (#251)
* Migrate routing from prod to new front v 0.5

* migrate category link to new fron v 0.5.5

* migrate category link to new fron v 0.0.8

* migrate category link to new-front caching issue

* window bug fix

* Category description v 0.0.1

* formatting and unnecessary quote marks deleted

* fix originalDescription assignment

* Added category description edit/add

* Added 409 error handling (need to add functionaly to buttons)

* changed: added emit for conflict popup

* changed: added api request to conflict handlng

* rename Article -> Category, ArticleContent -> CategoryItem

* minor rename fix

* changed: moved all description changes to a single function, emit call fixes, minor style fixes

* changed: category description conflict data sent to api fixes

* refactoring bug fix

* fix: if description exists no description shown in textarea

* fix: empty field in the Dialog

* changed: emit event from conflict-dialog refactoring and fix

* changed: 400 api error fix

* changed: old summary blink bug six

* minor fix

* hotfix: textare bug fix

* api change fix

* minor fix

* changed: fixed several time description saves failing

* Merge with develop - many bugs

* merge with develop - critical bug fix

* merge with develop bug-fixes

* refactoring

* bug fixes

* changed: replace textarea to markdown in category description. Need to do same with conflict dialog

* changed: resolved linter warnings, added markdown to merged window in conflicts dialog

* minor fix

* cancel, text-wrap fix

* minor fix

* minor fix

* minor fix and uid -> id in addDescription

* changed: minor fix 2

* small changes

* small refactoring

* part of refactoring, btn text bug fix

* move no-category description stub to same div where category description is being loaded

* move category to own component

* minor fixes, enable mobile layout

* small change

* small changes

* slot removed

* small changes

* throw err moved to else statement

* small changes

* minor fix

* small changes

* description button text and icon refactoring

* add description btn icon/text small refactoring
2019-02-04 12:57:28 +05:00
back API for requesting a single category/item/trait (#262) 2019-01-23 16:30:43 +03:00
docker/back Travis improvements (#253) 2019-01-02 17:07:52 +04:00
favicon Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
front Category description add edit (#251) 2019-02-04 12:57:28 +05:00
scripts Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
.gitignore Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
.hlint.yaml Add HLint rules and fix some suggestions (#261) 2019-01-23 09:29:39 +01:00
.travis.yml [WIP] Remove kinds and add hackage as option (#249) 2019-01-05 16:08:42 +05:00
INSTALL.md Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
Makefile Travis improvements (#253) 2019-01-02 17:07:52 +04:00
README.md Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
shell.nix Add custom shell.nix file 2017-10-09 09:30:41 +02:00
stack.yaml [WIP] Remove kinds and add hackage as option (#249) 2019-01-05 16:08:42 +05:00

Aelve Guide

Build status BSD3 license

The beta version is running at guide.aelve.com. The most complete section yet is the one about lenses.

Installation instructions and the explanation of config variables (in config.json) are here: INSTALL.md. Don't be afraid to install it locally it's very easy! You don't need to set up any databases or anything like that, and you can get a full copy of the data from the site by simply cloning it from Github.

Contributing

If you want to contribute but don't know where to start, grep the source for [very-easy] and [easy], or look at these issues:

  • “your first pull request” really easy things, with detailed “how to fix it” instructions
  • “your second pull request” less easy things, which assume that you already know where stuff happens in the code
  • “not-fleshed-out idea” discussion issues (“should we have users? what better ways are there to present pros and cons?”) which you can help with even if you don't know Haskell
  • “design” issues about design (which I'm not good at, and so help is wanted)

Testing

You need chromedriver and selenium-server-standalone installed (those are the package names on Arch Linux). Then you can do

$ java -jar /usr/share/selenium-server/selenium-server-standalone.jar
$ make back/test

Notes

When you see something like

-- See Note [acid-state]

it means that there's an extensive comment somewhere else in the code, which you can find by grepping for Note [acid-state]. This convention was stolen from GHC. If you know some plugin for Emacs that would help with jumping to comments (even if those comments would have to be formatted differently), let me know.