Javi Martín d0d1c9972c Remove unused variables following their parent
There's a very common pattern in our test, where the setup only has two
lines:

variable = create(:something)
unused_variable = create(:something_else, something: variable)

In this case, since there's a blank line below these ones and then we'll
get to the body of the test, and the second variable is going to be
created based on the first variable, we can remove the useless
assignment and the readability is still OK.

Another option we almost unanimously discarded was:

variable = create(:something)
_unused_variable = create(:something_else, something: variable)

We don't use it anywhere else, either.

One more option we considered but found a bit too much for simple tests:

variable = create(:something) do |something|
  create(:something_else, something: variable)
end

Then of course we could move the setup to `let` and `before` blocks, but
the tests could get over-structured really quickly.
2019-09-30 15:47:13 +02:00
2018-12-07 13:57:32 +01:00
2019-09-24 19:29:46 +02:00
2019-09-10 21:04:56 +02:00
2019-03-15 10:29:07 +01:00
2015-07-15 13:32:13 +02:00
2019-09-10 21:04:56 +02:00
2019-09-11 14:03:24 +02:00
2017-06-14 18:14:02 +02:00
2015-08-17 19:55:28 +02:00
2016-11-19 20:27:39 +01:00
2019-07-29 13:59:06 +02:00
2019-03-15 10:29:07 +01:00
2019-06-10 15:47:13 +02:00
2019-03-15 10:29:07 +01:00
2019-04-16 17:38:23 +02:00
2019-04-16 17:19:44 +02:00
2019-03-15 10:29:07 +01:00
2019-04-02 10:45:36 +02:00
2019-09-12 13:31:16 +02:00

CONSUL logo

CONSUL

Citizen Participation and Open Government Application

Build Status Code Climate Coverage Status Crowdin License: AGPL v3 Reviewed by Hound

Accessibility conformance A11y issues checked with Rocket Validator

Join the chat at https://gitter.im/consul/consul PRs Welcome

This is the opensource code repository of the eParticipation website CONSUL, originally developed for the Madrid City government eParticipation website

Documentation

Check the ongoing documentation at https://docs.consulproject.org to learn more about how to start your own CONSUL fork, install it, customize it and learn to use it from an administrator/maintainer perspective.

CONSUL Project main website

You can access the main website of the project at http://consulproject.org where you can find documentation about the use of the platform, videos, and links to the community space.

Configuration for development and test environments

NOTE: For more detailed instructions check the docs

Prerequisites: install git, Ruby 2.3.2, bundler gem, Node.js and PostgreSQL (>=9.4).

git clone https://github.com/consul/consul.git
cd consul
bundle install
cp config/database.yml.example config/database.yml
cp config/secrets.yml.example config/secrets.yml
bin/rake db:create
bin/rake db:migrate
bin/rake db:dev_seed
RAILS_ENV=test rake db:setup

Run the app locally:

bin/rails s

Prerequisites for testing: install ChromeDriver >= 2.33

Run the tests with:

bin/rspec

You can use the default admin user from the seeds file:

user: admin@consul.dev pass: 12345678

But for some actions like voting, you will need a verified user, the seeds file also includes one:

user: verified@consul.dev pass: 12345678

Configuration for production environments

See installer

Current state

Development started on 2015 July 15th. Code was deployed to production on 2015 september 7th to decide.madrid.es. Since then new features are added often. You can take a look at the current features at the project's website and future features at the Roadmap and open issues list.

License

Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)

Contributions

See CONTRIBUTING.md

Description
This is the repository for a demo instance for Nairobi County
Readme 104 MiB
Languages
Ruby 76.1%
HTML 14.6%
SCSS 5.7%
JavaScript 2.3%
Python 1.2%