mms-client 1.0.5__py3-none-any.whl → 1.0.6__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. {mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/METADATA +2 -2
  2. {mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/RECORD +4 -4
  3. {mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/LICENSE +0 -0
  4. {mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/WHEEL +0 -0
{mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/METADATA RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: mms-client
3
- Version: 1.0.5
3
+ Version: 1.0.6
4
4
  Summary: API client for accessing the MMS
5
5
  Author: Ryan Wood
6
6
  Author-email: ryan.wood@electroroute.co.jp
@@ -43,7 +43,7 @@ The MMS has two separate endpoints, depending on whether you want to access mark
43
43
  # Object Hierarchy
44
44
  The object hierarchy contained in this project is not trivial, and perhaps that reflects a bit of overengineering on our part. However, we chose the paradigm we did to reduce the number of types which had to be exposed to the user. The diagram below indicates how this hierarchy works:
45
45
 
46
- ![MMS Client Object Hierarchy](/docs/mmsclient_hierarchy.drawio.png)
46
+ ![MMS Client Object Hierarchy](https://github.com/ElectroRoute-Japan/mms-client/blob/main/docs/mmsclient_hierarchy.drawio.png)
47
47
 
48
48
  Note that there are some types here that are shared between the request and response: mainly, anything inheriting from `mms_client.types.base.Envelop` or `mms_client.types.base.Payload`. For users of the client, only the Payload types need ever be used. Everything else has been obfuscated away, so it is unecessary for the user to have access to these. However, we will explain our reasoning here to provide additional context.
49
49
 
{mms_client-1.0.5.dist-info → mms_client-1.0.6.dist-info}/RECORD RENAMED
@@ -28,7 +28,7 @@ mms_client/utils/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,
28
28
  mms_client/utils/errors.py,sha256=jYdlG4OPI82s0fJcXCRNlKeEixDUSSAxjs_7C16qVL4,2306
29
29
  mms_client/utils/serialization.py,sha256=Zp1pZvrWcbV4p_PERS5e9zNKPSeHQFijYzJiby3y0Pk,25206
30
30
  mms_client/utils/web.py,sha256=fcdCtdDrHBPyhIlTcyiuAk3D3TlW8HmUw-wGfpG4KTA,9653
31
- mms_client-1.0.5.dist-info/LICENSE,sha256=awOCsWJ58m_2kBQwBUGWejVqZm6wuRtCL2hi9rfa0X4,1211
32
- mms_client-1.0.5.dist-info/METADATA,sha256=ipQzCCXjjlPxB3CgR_xRVWBp-t22GnEq_lmyC0mlXuU,13782
33
- mms_client-1.0.5.dist-info/WHEEL,sha256=Zb28QaM1gQi8f4VCBhsUklF61CTlNYfs9YAZn-TOGFk,88
34
- mms_client-1.0.5.dist-info/RECORD,,
31
+ mms_client-1.0.6.dist-info/LICENSE,sha256=awOCsWJ58m_2kBQwBUGWejVqZm6wuRtCL2hi9rfa0X4,1211
32
+ mms_client-1.0.6.dist-info/METADATA,sha256=sImN-laCo5emcrt6KlfJZGmdb85XlBbTumjRlmIkUZQ,13840
33
+ mms_client-1.0.6.dist-info/WHEEL,sha256=Zb28QaM1gQi8f4VCBhsUklF61CTlNYfs9YAZn-TOGFk,88
34
+ mms_client-1.0.6.dist-info/RECORD,,