-
### Expected behavior
SDK user must be able to start the blockchain application with the minimum code required.
```js
const {Application, sampleGenesisBlock } = require('lisk-framework');
const ap…
-
### Expected behavior
It should log SQL queries when we enable it in config.
### Actual behavior
It doesn't log the queries.
### Steps to reproduce
Include `query` in `logEvents` array in config,…
-
## Parent https://github.com/LiskHQ/lisk/issues/3153
### Expected behavior
Update the new README file for the application-level folder. Describe:
- The general idea of the application level.
- How…
-
### Expected behavior
Now jenkins runs the network test, so the test should pass.
### Actual behavior
Network test is constantly failing
-
## Parent https://github.com/LiskHQ/lisk/issues/3153
### Expected behavior
Create the new README file for the framework. Describe the general idea and interaction between modules, components and con…
-
### Expected behavior
Some tests are failing in the `development` branch
### Actual behavior
All tests should pass in the `development` branch
### Steps to reproduce
Build `development`…
-
### Expected behavior
No typos in Readme :smile_cat:
### Actual behavior
Small typo found, see image
![image](https://user-images.githubusercontent.com/1993505/54282747-f3434e80-459c-11e9-8800…
-
### Expected behavior
Should accept ENV var to modify app behavior.
### Actual behavior
Schema validation error:
```js
[ { keyword: 'type',
dataPath: '.modules.http_api.httpPort',
…
-
### Description
Change of the folder structure to clearly shows the difference of `core` and `lisk`
- build
- config
- docker
- src
- test
- Jenkinsfile related to the application
should b…
-
### Expected behavior
There should be only one configuration file for one network.
### Actual behavior
Right now we have one file `exceptions.js` for each network, which actually is part of config…