Conversation
doc/contribution.md
Outdated
|
|
||
| ## Coding standards | ||
|
|
||
| Please follow `clj-style` and `kondo` instructions. `Kibit` isn't a showstopper, but PRs are more welcomed if not |
There was a problem hiding this comment.
"...more welcome if they don't break kibit.'
doc/contribution.md
Outdated
|
|
||
| ## Submitting a PR | ||
|
|
||
| Before you are submitting a PR be sure: |
There was a problem hiding this comment.
"Before you submit a PR be sure:"
doc/contribution.md
Outdated
| - the PR has an issue in GitHub, with a good description | ||
| - you have added tests | ||
| - you provided an example project for a new feature | ||
| - All PRs need at least two approvals |
There was a problem hiding this comment.
This doesn't really belong in a list of things to check. Maybe just move it to its own paragraph after the list.
doc/contribution.md
Outdated
|
|
||
| ## Generating API Docs | ||
|
|
||
| This is done with using [mermaid-cli](https://github.com/mermaid-js/mermaid-cli) and a forked version |
There was a problem hiding this comment.
either "with" or "using". Not both.
doc/contribution.md
Outdated
| This is done with using [mermaid-cli](https://github.com/mermaid-js/mermaid-cli) and a forked version | ||
| of [Codox](https://github.com/Flexiana/codox). | ||
|
|
||
| We're using mermaid-cli for render UML-diagrams in markdown files, see the `doc/conventions_template.md` for example. |
There was a problem hiding this comment.
"...mermaid-cli to render..."
| of [Codox](https://github.com/Flexiana/codox). | ||
|
|
||
| We're using mermaid-cli for render UML-diagrams in markdown files, see the `doc/conventions_template.md` for example. | ||
| These files need to be added to the `/script/build-docs.sh` . For using it you need to have `npx`. |
doc/conventions.md
Outdated
|
|
||
| ## Overview | ||
|
|
||
| The diagram bellow gives you an overview, how a request is processed in Xiana based applications. |
There was a problem hiding this comment.
"... an overview of how a request..."
doc/conventions.md
Outdated
|
|
||
| An interceptor is a pair of unary functions. Each function must recieve and return a state map. You can look at it as on an analogy to AOP's around aspect, or as on a pair of middlewares. They work mostly the same way as [pedestal](http://pedestal.io/reference/interceptors) and [sieppari](https://github.com/metosin/sieppari) interceptors. | ||
| Xiana provides a set of base [interceptors](interceptors.md), for the most common use cases. | ||
| An interceptor is a pair of unary functions. Each function must recieve and return a state map. You can look at it as on |
There was a problem hiding this comment.
"look at it as an analogy...."
doc/conventions.md
Outdated
| ## Interceptors error handling: | ||
|
|
||
| The interceptor executor handles the exceptional states like sieppari does. If an exception happens, it tries to handle | ||
| first in the same interceptor. If it has and `:error` handler, it will call it, otherwise it'll search for `:error` |
doc/conventions.md
Outdated
|
|
||
| The interceptor executor handles the exceptional states like sieppari does. If an exception happens, it tries to handle | ||
| first in the same interceptor. If it has and `:error` handler, it will call it, otherwise it'll search for `:error` | ||
| handlers for the beginning of the interceptor queue. When and `:error` function found, and matched with the given |
There was a problem hiding this comment.
Should "for" be "from"?
"When an :error function..."
doc/conventions.md
Outdated
| The interceptor executor handles the exceptional states like sieppari does. If an exception happens, it tries to handle | ||
| first in the same interceptor. If it has and `:error` handler, it will call it, otherwise it'll search for `:error` | ||
| handlers for the beginning of the interceptor queue. When and `:error` function found, and matched with the given | ||
| exception, the executor calls the queue `:leave` functions in reserved order, where the handler has been found. |
There was a problem hiding this comment.
maybe "...calls the queue of :leave functions in reverse order from where the handler was found.
doc/conventions.md
Outdated
| handlers for the beginning of the interceptor queue. When and `:error` function found, and matched with the given | ||
| exception, the executor calls the queue `:leave` functions in reserved order, where the handler has been found. | ||
|
|
||
| This diagram shows how the error cases handled: |
doc/conventions_template.md
Outdated
| - request-data | ||
| - response | ||
|
|
||
| This structure is very volatile, will be updated quite often on the application's life cycle. |
There was a problem hiding this comment.
"...volatile, and will be updated..."
doc/conventions_template.md
Outdated
|
|
||
| - Interceptors: | ||
|
|
||
| Add, consumes or remove information from the state map. More details in [Interceptors](#interceptors) section. |
doc/conventions_template.md
Outdated
|
|
||
| The action conventionally is the control point of the application flow. This is the place were you can define how the | ||
| rest of your execution flow would behave. Here you can provide the database query, restriction function, the view, and | ||
| the additional side effect functions are you want to execute. |
There was a problem hiding this comment.
"...functions that you want to..."
doc/conventions_template.md
Outdated
|
|
||
| ## Dependencies | ||
|
|
||
| Modules can depend on external resources, configurations, as well as on other modules. These dependencies are added to |
There was a problem hiding this comment.
"...external resources and configurations..." (or maybe and/or)
doc/conventions_template.md
Outdated
|
|
||
| ## Interceptors | ||
|
|
||
| An interceptor is a pair of unary functions. Each function must recieve and return a state map. You can look at it as on |
There was a problem hiding this comment.
"...look at it as an analogy..."
doc/conventions_template.md
Outdated
| The interceptor executor handles the exceptional states like sieppari does. If an exception happens, it tries to handle | ||
| first in the same interceptor. If it has and `:error` handler, it will call it, otherwise it'll search for `:error` | ||
| handlers for the beginning of the interceptor queue. When and `:error` function found, and matched with the given | ||
| exception, the executor calls the queue `:leave` functions in reserved order, where the handler has been found. |
There was a problem hiding this comment.
Same as the non template version.
| ### 2. Set initial value of re-frame database | ||
|
|
||
| File *src/frontend/todo_app/db.cljs* contains initial value of re-frame databse. Inside of this file replace value of *default-db* to following: | ||
| File *src/frontend/todo_app/db.cljs* contains initial value of re-frame databse. Inside of this file replace value of * |
There was a problem hiding this comment.
"...change the value of default-db to the following..."
| @@ -0,0 +1,108 @@ | |||
| <!DOCTYPE html PUBLIC "" | |||
There was a problem hiding this comment.
This will need regenerating from the corrected .md file?
Title:
Update documentation for release v0.5.0-rc3
Description
Updated markdown files, and build-docs.sh to support UML integration
Using forked codox for support markdown anchors - See in contribution.md
Tester info
Pls go through as an english teacher 😉
Completion Checklist