hasadna / hasadna/knesset-data-python

dataservice should support unified field for id / desc fields from new knesset API

Open
#13 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
2
Forks
14
PR merge metrics
No merged PRs in 30d

Description

@OriHoch:
> the new knesset API have a lot of these fields where you have somethingID and related somethingDesc
worth to create a new KnessetDataServiceField class which will handle it automatically -
so instead of defining those two fields, you would define only 1 field:
("type", KnessetDataServiceIdDescriptionField("SubType", "type of the bill"))
behind the scenes this field can expose a python tuple of (id, description)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.