This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
PyLiquidPlanner
===============

[![Build Status](https://travis-ci.org/impulse-cloud/pyliquidplanner.svg?branch=master)](https://travis-ci.org/impulse-cloud/pyliquidplanner)

Python wrapper for the Liquid Planner REST API.

The code is inspired by [PyXero](http://github.com/freakboy3742/pyxero) and aims to offer an ORM style of accessing the API.

## Installation

At present, the library is not available in PyPI but can be installed from GitHub:

```
pip install git+git://github.com/impulse-cloud/pyliquidplanner.git
```

Alternatively, if you don't have Git installed:

```
pip install --upgrade https://github.com/impulse-cloud/pyliquidplanner/tarball/master
```

## Quickstart:

In addition to the instructions shown here, you will need to follow the [Liquid Planner API Guide](http://www.liquidplanner.com/assets/api/liquidplanner_API.pdf) and the [Types Documentation](https://app.liquidplanner.com/api/help/types) to see which fields are available.

Use your Liquid Planner login to construct some credentials:

```python
>>> from liquidplanner.auth import BasicCredentials
>>> credentials = BasicCredentials(<email>, <password>)
```

Then create an API instance:

```python
>>> from liquidplanner import LiquidPlanner
>>> lp = LiquidPlanner(credentials)
```

You can then access the various types of entities by name. For example, here is a list of all the projects in your workspace:

```python
>>> projects = lp.projects.all()
>>> for p in projects:
>>> print p['name']
```

## Workspaces

With the exception of `account` and `workspaces`, all other entities require a workspace to be specified. When instantiated, the API requests a list of available workspaces and defaults to the first returned. You can disable this check by passing the `use_first_workspace` argument.

```python
>>> lp = LiquidPlanner(credentials, use_first_workspace=False)
```

You must then set the API's `workspace_id` manually.

```python
>>> workspaces = lp.workspaces.all()
>>> lp.workspace_id = workspaces[1]['id']
```

## Using the API

The following entities are supported at present:

* Account
* Workspaces
* Activities
* Checklist Items
* Clients
* Comments
* Custom Fields
* Documents
* Events
* Folders
* Links
* Members
* Milestones
* Packages
* Projects
* Tags
* Tasks
* Teams
* Timesheets
* Tree Items
* Webhooks

### Reading

This library wraps the objects returned in a `dict` like object. This is done so that related
items can be accessed via the objects returned (see [Associated Objects](#associated-objects) below). Otherwise the data is returned as-is, except for dates which are converted into Python `datetime.datetime` objects.

Use `all()` to get a full list of entities.

```python
>>> all_clients = lp.clients.all()
```
Most API options are supported, including:

* `include` - fetch related entities too
* `filters` - filter the list of items returned
* `order` - sort order of results
* `limit` - limit the number of objects returned

Use `get()` to fetch a specific entity by id.

```python
>>> client = lp.clients.get(1234)
```

Most API options are supported, including:

* `include` - fetch related entities too
* `depth` - max depth when fetching tree items

### Creating

Use `create()` to insert a new entity.

Note: The LiquidPlanner REST API requires the data to be wrapped with the single entity name. For example `{'client': {'name': 'My Client'}}`. This library takes care of the outer part, so you only need to worry about `{'name': 'My Client'}}`.

```python
>>> client = lp.clients.create({'name': 'My Client'})
```

### Updating

Updating records is similar to creating, but the record id must be supplied.

```python
>>> client = lp.clients.update(1234, {'name': 'New Client Name'})
```

### Associated Objects

The objects returned by `all()` and `get()` look and behave like Python `dict`s, but have a few properties available that allow access to associated objects. These properties have all the functionality of the main API endpoints.

For example, you can retrieve comments for a given task:

```python
>>> task = lp.tasks.get(1234)
>>> comments = task.comments.all()
```

Or create a comment for a given task:

```python
>>> task = lp.tasks.get(1234)
>>> comment = task.comments.create({"description": "This is my comment"})
```

Updating and deleting works similarly.

Note: This functionality is not available when you use the `include` parameter to make associated objects available for an `all()` or `get()` request. Only the outer object(s) have associated objects available.

### Convenience Methods

For certain objects, the API supports various convenince methods. The wrapper does not attempt to filter the convenience methods to their applicable object types, it is up to the developer to use the Liquid Planner API Guide.

Supported convenience methods:

* Tree Items
* Update Assignment
* Reorder Assignments
* Delete Assignment
* Events, Projects, Tasks, etc.
* Move Before / After
* Tasks
* Package Before / After
* Track Time
* Timer Start / Stop / Commit / Clear
* Documents
* Thumbnail
* Download
* Workspaces
* Comment Stream
* Upcoming Tasks
* Changes

## Future

This library is very new and still a work in progress. Some things I would like to support in future include:

* Support for the 'convenience methods' (e.g. assignments, re-ordering)
* Save and retrieve of attachments
* More tests

## Tests

To run the unit tests, run the following from the root directory of the project:

```
$ python setup.py test
```

This is will install any test dependencies (Mock) into your environment and execute the unit tests.

## Contributing

Contributions are most welcome by submitting a pull request. Please try to include test coverage of any new features or bug fixes.

If you have any problems with PyLiquidPlanner, you can [log an issue](http://github.com/impulse-cloud/pyliquidplanner/issues) on GitHub.
Release History

Release History

0.0.2

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.0.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
pyliquidplanner-0.0.2.tar.gz (8.3 kB) Copy SHA256 Checksum SHA256 Source Aug 25, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting