hasadna/open_pension

:chart_with_upwards_trend: Open Pension is a "Hasadna" project, that aimed to revealing the secrets behind the Israeli pension market.

open_pension's Issues

Integrate Webpack

And move to Angular 2.0 RC

Adding semantic ui front end.

https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.1.8/semantic.min.css
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.1.8/semantic.min.js

Add i18n_patterns.

Create a wiki

Write a wiki with Moses, and docs for the models.

Create Models

Models translation support

We should support translations for models with textual fields.

Angular.js 2 basic components

Create a basic Angular 2.x app

Managing Body summary endpoint for the landing page

Create a pycodestyle test.

Reference: https://pypi.python.org/pypi/pycodestyle/1.8.0.dev0

Create a simple test for angular.

• Create a unit test with jasmine.
• Create an e2e test with protractor.

Tests.

Write a test to check the index.html page of Django (that's just for the sake of start small, we'll write proper tests in the future).

Reference: https://docs.djangoproject.com/en/1.9/topics/testing/

Create managing-body-list Component

Refactor to use Angular-cli

Reference: https://github.com/angular/angular-cli

Fix the router.

• Upgrade to RC3.
• Fix the router.
• Add a child route for managing-bodies component.

Handling CORS

Can't do a get request from angular, get a cross-origin error.

Get all the data for the managing body endpoint.

• Total amount in a pension.
• The percentage from the total amount in all the pensions.
• The percentage changed from the last 4 months.

Create hero header component.

Show search component inside it.

Create managing-body component

Create op-search-result component

Reference: link

API version

We need a versioning for our api endpoints.
Reference: http://www.django-rest-framework.org/api-guide/versioning/

The client will pass the version number in the header.
Reference: http://www.django-rest-framework.org/api-guide/versioning/#acceptheaderversioning

Refactor ManagingBody model.

• Move the ManagingBody model to a separate file (from ManagingBody.service).
• Change it from export interface.. to export class...

Create issue and PR templates.

Create a "Send Feedback" link.

Create a "send feedback" Popup (/Modal dialog) with a name, email and text inputs, for people send us email with feedback about the website.
Don't forget to add there a "Send" button to send it to us.

Just create the dialog component and the logic to pop it up, don't worry about sending an email, we'll handle it later (in another issue).

Client task runner (gulp)

Import dummy data

Add i18n for Angular.

Reference: https://github.com/angular/i18n

Add SASS loader to webpack.

Reference: https://github.com/jtangelder/sass-loader

Refactor ManagingBody.

• Move managing-body-list, managing-body, managing-body-detail, to one directory called managing-bodies.

Review models.

@ranmoshe Review the models, check that there are represent the entities that moshe describe here: https://drive.google.com/drive/u/0/folders/0B7RkqHKoREPqRnZiRnZoWFF1ek0

Add the LICENSE file with appropriate copyright

Just the MIT file with the appropriate year, name and email

Edit humans and cleanup requirements.

Handle translation on the managing body endpoint

Since the label field is now translated on the Managing Body model, we should return all the available translations on the endpoint.

@nirgn975
Not sure if we should return all translations or just the relevant one dependent on the user request ...

.js and map.js files in seperate /build folder

Pull data and display it.

Pull the data from django db, create endpoint, and show it in angular view.

Add privacy policy link

Add a link for that in the footer.
The "privacy policy" text should be like in http://www.openpension.org.il/#/privacy

Integrate Travis-CI

Create managing-body-detail component

Chart skeleton with d3.js

http://bl.ocks.org/kerryrodden/7090426

https://www.jasondavies.com/coffee-wheel/

Semantic-ui check

Miscellaneous

• In every component, delete the element selectors we don't use.
• Delete the provider from managing-body-list and add it to the app.ts.
• move the managing-body-list component from the component directory to the app directory (delete the components directory).
• Add a space between the import of the components (like from {Observable} to { Observable }) In link
• Make sure every component selector start with op-.

i18n infrastructure

We need to make sure the infrastructure for i18n is good to go.

Fix managing body, Home, About components.

Research css architecture options

in this tutorial they include the component's styling in a file that they import in the component:

I like the idea, it makes the idea of reusable components stronger
Do we want to work like this too?

they also use something like shadow css (i think.... or what is the :host selector)
would be nice if someone can research this option

Finish create Docker.

• Container for the database - PostgreSQL.
• Container for the back end - Django.
• Container for the front end - Angular 2.
• Container for the server - Nginx.

Finish Docker for frontend

Refactor to use moduleId

• Use moduleId: module.id, as the first selector in each component.
• Remove the app/... from the templateUrl, etc..

Child router.

The router of /managingbody/:id should be a child route in managing-body component. Now he is at app.ts.

Reference: http://a2-first-look.azurewebsites.net/examples/router-child/plnkr.demo.html?bust=1463687660843
Look at app/app.component.ts file, you'll see the main path for characters (for example) and then look at app/characters/characters.component.ts file, you'll see the child router for the characters path.

Create op-search-result-list component

Reference: link

Add text for the about page.

http://www.openpension.org.il/#/about

pi managing body endpoint.

https://github.com/d3/d3/wiki/Partition-Layout