Expression syntax for composing and manipulating Python functions.
from fungebra import Function
from external_library import other_func
@Function
def my_func():
from functools import partial, reduce | |
import operator | |
from typing import Callable, Iterable, Union | |
from funcy import compose, identity | |
class Function: | |
"""Function wrapper with composition methods.""" | |
def __init__(self, func: Union[Callable, "Function"]): |
There are 5 Pull Requests, which I recommend should be merged in the following order:
Given these pairs:
patient,referral
p29286416172,r19529956641
p49607832635,r19293807841
p69929249091,r19057659047
p90250665558,r19821510137
p10572084327,r19585361336
p30893500781,r19349212531
p51214917243,r19113063730
from collections import namedtuple | |
class ImmutableNamespaceMeta(type): | |
def __new__(cls, name, bases, dct): | |
x = super().__new__(cls, name, bases, dct) | |
public = {key: value for key, value in dct.items() if not key.startswith("_")} | |
typ_ = namedtuple(name + "Type", public.keys()) | |
return typ_(**public) | |
This document provides some JSON examples to aid with re-integration of consumers to breaking API changes for patient records brought about by NDMS-1984.
Included are happy path before/after examples for common cases:
as well as some canonical invalid payloads.
referral_clinicians
, under an attribute with the same name.referral_clinician
contains:
clinician
(see below)organisation_uid
referencereferral_clinician_role_uid
reference (always null
)referral_uid
reference (always the same as the outer referral
)