- Reword headings for consistency
- Polish Markdown syntax
- Link to correct docs in Prerequisites section
There are no significant substantive changes in the instructions here,
just reworking of the existing content.
Prior to this change, DAO setup instructions and information were
interspersed within dev-setup.md, making it confusing to the uninitiated
reader what they need to do in order to get up and running with a basic
local dev environment. All the DAO setup stuff is essentially optional,
so separating it out into its own doc makes sense.
Now, dev-setup.md is dedicated to the task of getting set up with a
self-contained local development environment, and readers can follow the
DAO setup instructions separately if and when they need to.
Both docs need to be further revised and cleaned up, but that will come
in subsequent commits.
The CONTRIBUTING.md file must be located in the root directory of a
project (or within a .github directory) in order to be recognized by
GitHub and presented to users during the process of filing an issue
or pull request. It doesn't do any good within the docs/ directory.
This doc was originally transcribed from #511, then moved to the wiki,
then moved here. Removing it now as (a) it's not clear this is of value to
anyone other than the original author and (b) this approach is not
necessarily something we want to advertise or promote.
Updating to the latest shadow plugin version will resolve the following
deprecation warning:
> Task :desktop:shadowJar UP-TO-DATE
Registering invalid inputs and outputs via TaskInputs and TaskOutputs
methods has been deprecated. This is scheduled to be removed in Gradle
5.0. A problem was found with the configuration of task
':desktop:shadowJar'.
See: https://github.com/johnrengelman/shadow/issues/336
From the changes in isCryptoCurrency which return true in case of BTC
there have been some bugs. We changed the check to distinguish between
altcoin and fiat to check for BTC as base currency now.
That area would require a bigger refactoring...
We changed the earlier behaviour with delayed execution of chunks of the list as it caused
worse results as if it is processed in one go.
Main reason is probably that listeners trigger more code and if that is called early at
startup we have better chances that the user has not already navigated to a screen where the
trade statistics are used for UI rendering.
We need to take care that the update period between releases stay short as with the current
situation before 0.9 release we receive 4000 objects with a newly installed client, which
causes the application to stay stuck for quite a while at startup.
