Allow invoice subclasses to explicitly declare their exported columns and column names #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #100. Two class attributes,
export_columns_list
andexported_columns_map
, has been added toInvoice
, along with a class function_filter_columns()
. Subclasses ofInvoice
must now defineexport_columns_list
, containing the ordered list of columns that must be exported in their respective invoices. Subclasses can optional defineexported_columns_map
, containing mappings between "internal" column names and what their name should be when exported.The field name
RATE_FIELD
has been added toinvoice.py
. It was previously forgotten.