Merge pull request #1696 from daostack/release

Release 0.10.7

CHANGELOG.md

@@ -1,19 +1,32 @@
+## 0.10.7
+  - Features Added
+    - Added "Stake for Reputation Plugin" to the list of known plugins that can be registered to a DAO
+    - Use Tor.us and Metamask providers when running against xDAI network (removes Burner Connect)
+
+  - Bugs Fixed
+    - Display a proper msg for daos members with no reputation at the moment of a proposal creation
+    - Fix summing up the number of schemes open proposals
+    - Cosmetic improvement to the New Proposal button
+    - Fix to breadcrumbs relating to the new DAO landing page
+    - Don't display unregistered schemes in the Plugin Manager plugins dropdown
+
 ## 0.10.6
   - Features Added
     - new DAO landing page
     - added help text in the Plugin Editor popup
 
-    - Bugs Fixed
-      - Make sure proposer name doesn't overlap avatar on proposal history rows
+  - Bugs Fixed
+    - Make sure proposer name doesn't overlap avatar on proposal history rows
+
 
 ## 0.10.5
   - Features Added
     - change home page to show DAOs again instead of feed. Show separate "Your DAOs" section containing DAOs the user follows or is a member of, then the list of other DAOs below.
     - added support for embedded youtube and vimeo videos in proposal descriptions
     - recommended node.js version to build Alchemy is set to 12.16.2
     - upgrade to use subgraph v39_3
-    - add subgraph_endpoints.json so it could be read externaly
-    - add CENNZ ERC20 token to be showen as dao owned tokens/balance
+    - add subgraph_endpoints.json so it could be read externally
+    - add CENNZ ERC20 token to be shown as dao owned tokens/balance
 
   - Bugs Fixed
     - fix Torus not connecting on first try

README.md

@@ -18,8 +18,7 @@ While anyone can propose and predict, only people who hold reputation (voting po
 
 ## Dependencies:
 * [NVM](https://github.com/creationix/nvm#installation) can be helpful to manage different versions of node
-* [NodeJS 9.4 or greater + NPM](https://github.com/creationix/nvm#usage)
-* You will  need [alchemy-server](https://github.com/daostack/alchemy-server) running locally for the app to function
+* [NodeJS 12.6.2 or greater + NPM](https://github.com/creationix/nvm#usage)
 
 ## Installation
 
@@ -41,7 +40,7 @@ you can recreate the docker environment by installing an starting all [services
 The easiest way to start developing is to work with docker.
 Here is a quick setup; there are more detailed instructions in [here](./docs/development.md).
 
-After you have installed docker, run the following command to spin up ganache (with the migrated contracts), the caching server and the alchemy server:
+After you have installed docker, run the following command to spin up ganache (with the migrated contracts), the graph-node server:
 ```sh
 docker-compose up graph-node
 ```

docs/development.md

@@ -3,7 +3,7 @@
 There are different ways a developer can use the docker environment for development.
 
 Probably the most flexible way is to run the services that alchemy depends on in one terminal,
-and run the alchemy server in a separate terminal:
+and run the graph-node server in a separate terminal:
 
 ```sh
   # run this only if package.json has changed
@@ -41,27 +41,27 @@ See [docker](./docker.md) for details about the docker containers.
 
 # Helpful scripts
 
-# Developing @daostack/client in tandem with alchemy with npm link
+# Developing @daostack/arc.js in tandem with alchemy with npm link
 
 ## The setup
 
-Download and install the client package and use `npm link` for local development
+Download and install the arc.js package and use `npm link` for local development
 ```sh
-# get the dev branch from the client repository
-git clone https://github.com/daostack/client.git#dev
-cd client
+# get the dev branch from the arc.js repository
+git clone https://github.com/daostack/arc.js.git#dev
+cd arc.js
 npm install
 npm run build
 npm link
 cd ../alchemy # cd to the alchemy directory
-npm link @daostack/client
+npm link @daostack/arc.js
 ```
-Now you should find a link to your local `client` directory in `node_modules/@daostack/client`
+Now you should find a link to your local `arc.js` directory in `node_modules/@daostack/arc.js`
 
 ## The development cycle
 
-The alchemy webpack process uses the compiled `.js` files in `@daostack/client/dist`.
-That means that when you make changes in the typescript `.ts` files in the client library, they will not be picked up until they are compiled to new `dist/*.js` files. You can do that by running:
+The alchemy webpack process uses the compiled `.js` files in `@daostack/arc.js/dist`.
+That means that when you make changes in the typescript `.ts` files in the arc.js library, they will not be picked up until they are compiled to new `dist/*.js` files. You can do that by running:
 ```sh
 npm run build:watch
 ```

docs/fetchingandsubscribingdata.md

@@ -17,5 +17,5 @@ So the approach we are taking in Alchemy is the following.
 Fetch the data that is used by many subcomponents in a single query, before those components are rendered. When those subcomponents are rendered, they will be able to get their data directly  from the cache, and so will avoid a server request in step 2. An example of that pattern is found in the `DaoHistoryPage.tsx`
 
 *To avoid the cost of step 4:*
-The line `arcSettings.graphqlSubscribeToQueries = false;` overrides the client default behavior to open a subscription for each query. So, by default, step 4 is skipped. Instead, we insert, in strategic places, subscriptions to relatively big queries, that will update the cache only for the data that we need.
+The line `arcSettings.graphqlSubscribeToQueries = false;` overrides arc.js default behavior to open a subscription for each query. So, by default, step 4 is skipped. Instead, we insert, in strategic places, subscriptions to relatively big queries, that will update the cache only for the data that we need.
 An example of this pattern is in `SchemeProposalsPage.tsx`

docs/nodocker.md

@@ -4,10 +4,6 @@ You can run all needed services locally
 
 # Run app locally
 
-## Run the Alchemy Server
-1. If you want to be able to save and display the proposal titles and descriptions you will need the Alchemy Server app running.
-2. Follow instructions [here](https://github.com/daostack/alchemy-server)
-
 ## Working with Ganache without MetaMask
 1. Make sure plugins such as MetaMask or Parity extension are deactivated
 2. Run `npm run auto-start-ganache`