AASHE / python-membersuite-api-client / 88 / 2
78%
master: 78%

DEFAULT BRANCH: master
Ran
Files 24
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 92.65% (-2.8%) from 95.433%
88.2

push

travis-ci

web-flow 
Merge pull request #17 from AASHE/msql-shell

Misc improvements on a branch named for a feature that got deleted
# Improved
## exceptions.py
## security/models.py
# New
## membersuite_api_client.models.MemberSuiteObject.  A base MemberSuite object for PortalUser and Individual.
### Takes `membersuite_object_data` as argument.
This object data is the Zeep'ed XML representation of a concrete type of MemberSuiteObject, like PortalUser or Individual.
### Takes care of converting data to a `fields` dictionary.
Hangs this dictionary, named `fields`, on self.
### Sets self.id and self.extra_data.
## membersuite_object_factory() in utils.py
Takes `membersuite_object_data` as input, returns a MemberSuiteObject.
If factory "knows" about the type of MemberSuiteObject, that specific type of MSO is returned.  Otherwise, a generic MemberSuiteObject is returned.  Now it only knows of PortalUser and Individual.
Usage:
```python
import utils

membersuite_object_data = self.get_login_to_portal_response()["PortalUser"]
# Or something similar, probably more complicated, a list of string indices
# into the MemberSuite API response.

portal_user = utils.membersuite_object_factory(membersuite_object_data)

print(portal_user.get_username())
```
Maybe a factory is overkill, since you can make a MemberSuiteObject by simply constructing it with the appropriate Zeep object, e.g., `PortalUser(membersuite_object_data)`.

416 of 449 relevant lines covered (92.65%)

0.93 hits per line

Source Files on job 88.2