-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Permalink
Loading
Choose a base ref
{{ refName }}
default
Loading
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: consuldemocracy/consuldemocracy
base: 522660a
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: consuldemocracy/consuldemocracy
compare: 249bd9d
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 12 commits
- 37 files changed
- 1 contributor
Commits on Dec 22, 2020
-
Note we're using the code instead of the ID to get the goal in the URL. IMHO this is what most people would expect; visiting a URL with a "7" takes you to SDG number 7, and not to the one with "7" as a database ID. In order to avoid tests (either automated tests or manual tests) passing by coincidence due to the goal ID and the goal code being the same, I'm shuffling the codes before entering them in the databse. I've tried using `resolve` in the routes so the code is automatically taken into account, but it doesn't work since `resolve` cannot be used inside a namespace, and here we're within the `sdg` namespace.
Configuration menu - View commit details
-
Copy full SHA for 9917838 - Browse repository at this point
Copy the full SHA 9917838View commit details -
Configuration menu - View commit details
-
Copy full SHA for a7cfd58 - Browse repository at this point
Copy the full SHA a7cfd58View commit details -
Use different backgound colors for different goals
The same way it's done by the United Nations.
Configuration menu - View commit details
-
Copy full SHA for 6b79509 - Browse repository at this point
Copy the full SHA 6b79509View commit details -
Configuration menu - View commit details
-
Copy full SHA for 631f3a3 - Browse repository at this point
Copy the full SHA 631f3a3View commit details -
Simplify debates and proposals feed layout
Using the `:only-child` selector we can adjust widths with CSS and don't have to rely on methods calculating which features are available.
Configuration menu - View commit details
-
Copy full SHA for 829bbeb - Browse repository at this point
Copy the full SHA 829bbebView commit details -
Use flex layout instead of data-equalizer in feeds
Using data-equalizer is always hard due to the JavaScript it uses, while the flex layout works all the time.
Configuration menu - View commit details
-
Copy full SHA for 46d847c - Browse repository at this point
Copy the full SHA 46d847cView commit details -
Reuse code between feed components
They were all following the same format. Note we need to group the `see_all` translation keys together (the same way it's done with the `most_active` keys) so we don't have an unused translation warning. We're also moving the "see all" link in processes outside the feed content; the same way it's done in debates and proposals and removing unnecessary classes in the processes feed: the column class is causing the processes not to be aligned with the debates above them, and the margin bottom is not needed because the margin of the footer is already enough.
Configuration menu - View commit details
-
Copy full SHA for 0396ced - Browse repository at this point
Copy the full SHA 0396cedView commit details -
Configuration menu - View commit details
-
Copy full SHA for 48b0898 - Browse repository at this point
Copy the full SHA 48b0898View commit details -
Configuration menu - View commit details
-
Copy full SHA for ab47d91 - Browse repository at this point
Copy the full SHA ab47d91View commit details -
Separate the header from the feed content
We were having some style issues when adding the processes feed to the goal view because of this lack of separation. We're using a <section> tag so it's clear where the <header> tag belongs to.
Configuration menu - View commit details
-
Copy full SHA for 5792d7f - Browse repository at this point
Copy the full SHA 5792d7fView commit details -
We were jumping from h1 to h3 and some of these sections (cards and processes) had h3 tags inside them. My best guess is we were using h3 so the titles were smaller. So I'm adding a CSS mixin to easily use a font size of a different heading tag.
Configuration menu - View commit details
-
Copy full SHA for c9a3dcc - Browse repository at this point
Copy the full SHA c9a3dccView commit details -
Note the link to see all processes does not filter by goal because the legislation section does not have any search filters.
Configuration menu - View commit details
-
Copy full SHA for 249bd9d - Browse repository at this point
Copy the full SHA 249bd9dView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 522660a...249bd9d