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

Allow Budget Group names to be edited #2504

Merged
merged 12 commits into from
Mar 22, 2018
Merged

Conversation

bertocq
Copy link
Collaborator

@bertocq bertocq commented Mar 2, 2018

Where

What

This is a backport from Madrid's fork AyuntamientoMadrid#1265 that will close issue #2438

Deployment

As usual

Warnings

None

@bertocq
Copy link
Collaborator Author

bertocq commented Mar 2, 2018

Backport on hold, this doesn't work on preproduction environment AyuntamientoMadrid#1319

@bertocq
Copy link
Collaborator Author

bertocq commented Mar 14, 2018

Closing until madrid's fork gets it right AyuntamientoMadrid#1361

@bertocq bertocq closed this Mar 14, 2018
@bertocq bertocq deleted the budget_group_name_edit branch March 14, 2018 16:25
@voodoorai2000 voodoorai2000 restored the budget_group_name_edit branch March 22, 2018 09:16
We were having a problem were some groups where not updating correctly.

That was because it was finding the first group with that name. However
we were looking for another group with the same name from another budget

Apart from the group_id, we also get the budget_id in the params for
updating a group. By finding groups within that budget we get the
expected behaviour
To maintain order after editing a group’s name

We should probably add timestamps to `groups` and `headings` and order
by `created_at` instead
To maintain order after editing a heading’s name

We should probably add timestamps to `groups` and `headings` and order
by `created_at` instead

Could have done it in a separate PR, but gotta keep moving to other
priority issues. Creating issue for timestamps to do correctly and with
tests 😌
Changing a group’s `to_param` to return the slug instead of the id,
breaks many tests in the user facing interface

We should use slugs in upstream soon, but it should be done in a
separate PR, bringing the whole slug implementation from Madrid’s fork
and the corresponding test coverage
No need for deprecation warnings in release notes, this is an attribute
that was used temporarily but did not make it to a Release
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.

None yet

3 participants