ferraith/django-portfolio

django-portfolio's Issues

Implement an asset data grabber

The fundamental data (e.g. name) and dynamic data (e.g. share prices) shouldn't be entered manually by the user. There exists several finance platforms providing finance data for free. This data should be loaded from a suitable platform.

• Choose a finance platform for a mock-up
• Design and implement a generic interface for the grabber
• Implement a grabber for the chosen platform

Introduce a generic Asset model

Actually the portfolio data model only knows a stock which can be invested in. A more generic asset model (meta class) should be added. All tradable investments (like a stock) should be inherited from the asset class.

Improve string representation of models

Actually most models from the portfolio da model only have a meaning less string representation (__str__ (self)) like its id. The string representation should be replaced by a representation useful for the user.

Setup CI environment

A CI environment should be set up for the django-portfolio app.

• Evaluate pytest-django
• Write some sample unit tests for PercentageValidator #4
• Set up a travis-ci project
• Add execution of unit tests to CI project

Set display name and handle translations of models and fields

Actually all fields of the portfolio data model have no display name (verbose_name) set. Therefore these names are used for the user interface like the admin site.

• Fields should have a proper display name
• Models should have a singular and plural display name
• ugettext_lazy should be used to translate names with respect to the locale

Add ticker symbol

A field for the ticker symbol should be added to tradable assets.

Actually the maximum ticker symbol length is 8 characters:
https://www.nasdaqtrader.com/trader.aspx?id=StockSymChanges

PercentageValidator

In the data model there exists a DecimalFeld ter storing percentages. A validator should be implemented which checks if a value is a valid percentage.

Replace transaction type scalars with a transaction type class

For implementation of the transaction type enum the pattern described in the choices documentation is actually used. This should be replaced by more elegant TransactionType class.