Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix input fields for single locale organizations #1983

Merged
merged 2 commits into from
Oct 5, 2017

Conversation

mrcasals
Copy link
Contributor

@mrcasals mrcasals commented Oct 4, 2017

馃帺 What? Why?

Surveys for single locale organizations were broken and not filling the question body input fields properly. Now they do!

馃搶 Related Issues

馃摲 Screenshots (optional)

http://g.recordit.co/kVcdRIplPL.gif
Description

Public page:

@codecov
Copy link

codecov bot commented Oct 4, 2017

Codecov Report

Merging #1983 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1983      +/-   ##
==========================================
+ Coverage   98.46%   98.48%   +0.01%     
==========================================
  Files        1145     1145              
  Lines       25736    25737       +1     
==========================================
+ Hits        25341    25346       +5     
+ Misses        395      391       -4

@mrcasals mrcasals merged commit 2c63b9a into master Oct 5, 2017
@mrcasals mrcasals deleted the fix/survey-single-locale branch October 5, 2017 07:18
@ghost ghost removed the in-review label Oct 5, 2017
mrcasals added a commit that referenced this pull request Oct 5, 2017
* Fix input fields for single locale organizations

* Add CHANGELOG entry
mrcasals added a commit that referenced this pull request Oct 5, 2017
* Don't use models in migrations (#1921)

* Run seeds in the same process as migrations

So we can detect bad model usage inside migrations.

* Don't swallow errors in app generation

The `rails_command` method shells out the target command, but swallows
any errors that may happen. In my opinion, this is bad because we really
want these commands to succeed, and since the output is usually long,
you might not notice that they have failed. In addition, if errors are
swallowed, it's really hard to unit test generators!

* Remove hardcoded models from migrations

And add a regression test for development app generation. To ensure that
these errors can be properly caught in the future.

* Prefer `abort` to `exit 1`

* Remove unnecessary `ActiveRecord::Base.connection`

In migrations, all that stuff in directly available.

* Silence test output

* Fix app generators (#1931)

* Bundle less generator failure (#1938)

* Fix crash when running decidim executable

We can't asume bundler is available inside our generators, since it
will not when they are run through decidim executable.

Fixes the following crash:

```
/code/to/decidim/lib/generators/decidim/install_generator.rb:25:in
`bundle_install': uninitialized constant
Decidim::Generators::InstallGenerator::Bundler (NameError)
```

* Improve some test descriptions

* Test generator without flags

* Extract a shared example

* Extract test app name to a variable

And rename it so that specs don't fail on a freshly cloned repo (where
./tmp does not exist).

* Allow DB dropping to fail

For example, on freshly cloned repos. As a result, we no longer need to
check for CI here.

* Generate dev application in tests via bin/decidim

So we can give it the standard "test name" and it doesn't affect our
"real" development application.

* Centralize dependencies (#1958)

* Style fixes in template Gemfile

* Centralize dependencies to a single Gemfile

* Upgrade dependencies

* Require survey TOS field on admin (#1980)

* Require survey TOS field on admin

* Add CHANGELOG entry

* Fix puma dep

* Fix input fields for single locale organizations (#1983)

* Fix input fields for single locale organizations

* Add CHANGELOG entry

* Bump version to 0.6.6

* Downgrade graphiql-rails

* Update CHANGELOG

* Use latest docker image on CircleCI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants