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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add all budget changes #18

Closed
wants to merge 55 commits into from
Closed

Add all budget changes #18

wants to merge 55 commits into from

Conversation

javierm
Copy link
Owner

@javierm javierm commented Jun 1, 2020

Everything here.

microweb10 and others added 30 commits May 31, 2020 18:08
Previously the draft mode was a phase of the PB, but that had some
limitations.

Now the phase drafting disappears and therefore the PB can have the
status published or not published (in draft mode).

That will give more flexibility in order to navigate through the
different phases and see how it looks for administrators before
publishing the PB and everybody can see.

By default, the PB is always created in draft mode, so it gives you
the flexibility to adjust and modify anything before publishing it.
We've got a "publish" action, so having it as a hidden field as well is
a bit fragile and allows users to "unpublish" a budget (even, though, of
course, most admins wouldn't want to "hack" their own applcation).
The show action only renders edit, so it isn't really useful.
While this use is harmless since it's in the admin section and
publishing a published budget does nothing, it's good to use abilities
to define permissions so developers being inspired by existing code
follow this practice as well.
- Add main button to budgets
- Ability to attach an image to budgets
- Add main button to each phase of the budget
- Ability to edit the name of the budget phases
- Ability to attach an image to budget phases
- Ability to create single heading budgets step by step
- UX improvements on the participatory budgets (public and admin)
Taken from a later commit
Before, users needed to navigate to the list of groups in order to
add, edit or delete a group.

Also, they need to navigate to the list of groups first, and then to
the list of headings for that group in order to add, edit or delete a
heading.

Now, it's possible to do all these actions for any group or heading
from the participatory budget view to bring simplicity and to reduce
the number of clicks from a user perspective.
decabeza and others added 24 commits June 1, 2020 14:57
Appart from 'balloting', there are more phases between 'publishing_prices'
and 'finshed'. So, it doesn't make sense that the filter 'selected' is
only applied to those two. With this change the filter will be applied
as follow:

'not_unfeasible' for phases:
- informing
- accepting
- reviewing
- selecting
- valuating

selected for phases:
- publishing_prices
- balloting
- reviewing_ballots

winners for phases:
- finished
This clas was used before, but since the new style for budgets is not
needed anymore
Since this partial will only be rendered for budgets with only one
heading, it does not make sense to iterarte over all groups and headings
There was a big difference between the current budget and a specific
budget landing page. This didn't really make too much sense. Also, it
was not possible to know how a draft participatory budget will look
before it was published.
By unifying those two views now they will look quite similar and it
will be possible for administrators to preview any draft budget and to
know how the budget will look like before actually publishing it.
Improve styles for budgets voting phase
@@ -1,6 +1,6 @@
require "rails_helper"

api_types = GraphQL::ApiTypesCreator.create(GraphqlController::API_TYPE_DEFINITIONS)
api_types = GraphQL::ApiTypesCreator.create

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rails/SaveBang: Use create! instead of create if the return value is not checked. Or check persisted? on model returned from create. (https://rails.rubystyle.guide#save-bang)

@@ -29,7 +29,7 @@ def query
private

def consul_schema
api_types = GraphQL::ApiTypesCreator.create(API_TYPE_DEFINITIONS)
api_types = GraphQL::ApiTypesCreator.create

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rails/SaveBang: Use create! instead of create if the return value is not checked. Or check persisted? on model returned from create. (https://rails.rubystyle.guide#save-bang)

@javierm javierm changed the base branch from master to rails5.2_compatibility June 2, 2020 16:46
javierm pushed a commit that referenced this pull request Sep 29, 2021
Insert new texts in locale filse
@javierm javierm closed this Oct 25, 2021
javierm pushed a commit that referenced this pull request Mar 5, 2022
* #18 Partial implementation for user verification

* #18 Add validation for CNP

* #18 Add working implementation for validation

* #18 Fix unsafe stripping

* Add test for CNP validation, split up terms checkboxes

Add a very basic system spec for the new CNP verification flow.

Split up the checkbox to accept terms, residency, and adult status into
three separate checkboxes.

Co-authored-by: tsundokul <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants