API: Add endpoint for fetching location data #15162

ryelle · 2017-05-18T21:44:23Z

Fixes #15080 by adding a new endpoint /data/locations returning all available continents, countries, and states; with options to restrict to a continent or country.

GET /data # returns an index describing the following endpoints
GET /data/locations # returns all continents, countries and states.
GET /data/locations/<location> # if given a continent code, return all countries and states of that continent.
GET /data/locations/<location> # if given a country code, return all states of a country.

This returns data that looks like the following. It uses WC()->countries->get_* etc, so any filtered content should be reflected in the output.

[
	{
		"code": "NA",
		"name": "North America",
		"countries": [
			{
				"code": "AG",
				"name": "Antigua and Barbuda",
				"states": []
			},
			…
			{
				"code": "US",
				"name": "United States (US)",
				"states": {
					"AL": "Alabama",
					"AK": "Alaska",
					…

To test:

Run the unit test: phpunit tests/unit-tests/api/data.php
Manually test by loading the endpoint, /data/locations optionally with continent & country codes, ex /data/locations/eu, /data/locations/us, or fake data to see an error /data/locations/aa
/data lists an "index" view
All new endpoints should be restricted to store managers

claudiosanches

Missing schema in all classes too.

claudiosanches · 2017-05-18T22:46:21Z

includes/api/class-wc-rest-data-controller.php

+ * @author   WooThemes
+ * @category API
+ * @package  WooCommerce/API
+ * @since    2.6.0


Should be 3.1.0

claudiosanches · 2017-05-18T22:48:36Z

includes/api/class-wc-rest-data-controller.php

+ * @package WooCommerce/API
+ * @extends WC_REST_Controller
+ */
+class WC_REST_Data_Index_Controller extends WC_REST_Data_Controller {


Filename should match the class name.
The abstract class does not have anything special, so could remove the abstract class and use this class to be extended by WC_REST_Data_Location_Controller.

claudiosanches · 2017-05-18T22:50:08Z

includes/api/class-wc-rest-data-location-controller.php

+ * @author   WooThemes
+ * @category API
+ * @package  WooCommerce/API
+ * @since    2.6.0


claudiosanches · 2017-05-18T22:55:00Z

includes/api/class-wc-rest-data-location-controller.php

+						'type'        => 'string',
+					),
+					'country' => array(
+						'description' => __( 'Country name to restrict states list', 'woocommerce' ),


I think should change Continent name and Country name to 2 letter code or ISO 3166 Code.

claudiosanches · 2017-05-18T23:02:48Z

includes/api/class-wc-rest-data-location-controller.php

+ * @package WooCommerce/API
+ * @extends WC_REST_Controller
+ */
+class WC_REST_Data_Location_Controller extends WC_REST_Data_Controller {


Class name should be WC_REST_Data_Locations_Controller

mikejolley

@justinshreve This could use your eyes too.

mikejolley · 2017-05-19T10:46:21Z

includes/api/class-wc-rest-data-controller.php

+	 * @return WP_Error|WP_REST_Response
+	 */
+	public function get_items( $request ) {
+		$data    = array();


nitpick; alignment

mikejolley · 2017-05-19T10:49:44Z

includes/api/class-wc-rest-data-controller.php

+				'description' => __( 'List of supported continents, countries, and states; restricted to the given continent', 'woocommerce' ),
+			),
+			array(
+				'slug' => 'locations/<continent>/<country>',


Cc'ing @justinshreve here too for feedback. How important is continent when it comes to country codes? It feels kind of weird to require it just to get a list of states for a country - all countries are unique, ISO standard codes...

Yeah I think we could probably drop it.

I know settings will mostly be using /data/locations that returns everything, but in terms of other use cases where we might need specific states for a country - it does seem easier to not require the continent.

Is having just continent useful? We could just get rid of /data/locations/<continent> and only have /data/locations/<country>.

Although existing use cases don't need it (?) I think it can be useful. It might be needed in the shipping zone implementation.

mikejolley · 2017-05-19T10:51:20Z

includes/api/class-wc-rest-data-location-controller.php

+					),
+					'country' => array(
+						'description' => __( 'Country name to restrict states list', 'woocommerce' ),
+						'type'        => 'string',


Correct me if I'm wrong, but I believe we can define valid values for these can we not?

I'm not sure what you mean - do you mean whitelisting countries?

mikejolley · 2017-05-19T10:53:21Z

includes/api/class-wc-rest-data-location-controller.php

+
+		$data = array();
+		foreach ( $continents as $continent_code => $continent_list ) {
+			if ( isset( $request['continent'] ) && ( strtolower( $continent_code ) !== strtolower( $request['continent'] ) ) ) {


Since codes are always upper case (?) wouldn't it be simpler to just sanitize and uppercase the user input?

Since these codes are filterable, I don't think we can rely on them always being uppercase

mikejolley · 2017-05-19T10:54:16Z

tests/unit-tests/api/data.php

@@ -0,0 +1,134 @@
+<?php
+/**
+ * Tests for Data API.


ryelle · 2017-05-19T18:16:27Z

I think I've addressed the feedback here — renamed the classes and files, fixed my copy-paste issues 😣 , added schemas, and changed the endpoints so a continent code is not required to get a states list for one country. I'll update the main description to reflect this.

emdashcodes

Looking good! I left a few notes. Most minor coding standards things, but I did note a few small improvements.

emdashcodes · 2017-05-19T17:32:42Z

includes/api/class-wc-rest-data-controller.php

+/**
+ * REST API Data controller
+ *
+ * Handles requests to the /data/location endpoint.


Minor typo. Should be /data/locations.

emdashcodes · 2017-05-19T17:49:25Z

includes/api/class-wc-rest-data-controller.php

+ *
+ * Handles requests to the /data/location endpoint.
+ *
+ * @author   WooThemes


Minor: Should be Automattic now.

(@mikejolley Looks like we still need to run a script on existing files at some point).

emdashcodes · 2017-05-19T17:50:16Z

includes/api/class-wc-rest-data-controller.php

+	}
+
+	/**
+	 * Check whether a given request has permission to read site data


Minor: Doc comments should end w/ punctuation for consistency.

emdashcodes · 2017-05-19T17:50:44Z

includes/api/class-wc-rest-data-controller.php

+	}
+
+	/**
+	 * Return the list of data resources


Minor: Doc comments should end w/ punctuation for consistency.

emdashcodes · 2017-05-19T17:50:55Z

includes/api/class-wc-rest-data-locations-controller.php

@@ -0,0 +1,146 @@
+<?php
+/**
+ * REST API Data controller


Punctuation.

emdashcodes · 2017-05-19T17:58:06Z

includes/api/class-wc-rest-data-controller.php

+
+		$context = ! empty( $request['context'] ) ? $request['context'] : 'view';
+		$data = $this->add_additional_fields_to_object( $data, $request );
+		$data = $this->filter_response_by_context( $data, $context );


I think we can just pass in view here since there won't end up being an edit context, like we do in the system status controller. That would allow us to drop line 109.

emdashcodes · 2017-05-19T18:05:53Z

includes/api/class-wc-rest-data-controller.php

+				'slug' => 'locations',
+				'description' => __( 'List of supported continents, countries, and states', 'woocommerce' ),
+			),
+			array(


I'm not sure if this second should be returned here at the root. I think the locations resource and in the future currencies would be here, but not anything one level down.

emdashcodes · 2017-05-19T18:07:05Z

includes/api/class-wc-rest-data-locations-controller.php

+	 * @return WP_Error|WP_REST_Response
+	 */
+	public function get_items( $request ) {
+		$continents = WC()->countries->get_continents();


Alignment needed for all 5 of these lines.

emdashcodes · 2017-05-19T18:15:07Z

tests/unit-tests/api/data.php

+		$this->assertEquals( 200, $response->get_status() );
+		$this->assertTrue( is_array( $locations ) );
+		$this->assertGreaterThan( 1, count( $locations ) );
+		$this->assertTrue( isset( $locations[0]['code'] ) );


We can use assertNotEmpty( $locations[0]['code']) here instead, and on other similar checks.

emdashcodes · 2017-05-19T18:17:12Z

tests/unit-tests/api/data.php

+		$response = $this->server->dispatch( new WP_REST_Request( 'GET', '/wc/v2/data' ) );
+		$index = $response->get_data();
+		$this->assertEquals( 200, $response->get_status() );
+		$this->assertEquals( 2, count( $index ) );


We could use assertCount here instead: $this->assertCount( 2, $index );

(I know other API tests are doing assertEquals too, but would be good to fix those in the future).

emdashcodes · 2017-05-19T18:30:33Z

Some quick notes on responses:

When requesting a specific country (say https://:site/wp-json/wc/v2/data/locations/CA) I think it would make sense to drop off the continent info. So instead of

[
  {
    "code": "NA",
    "name": "North America",
    "countries": [
      {
        "code": "CA",
        "name": "Canada",
        "states": {
          "AB": "Alberta",
          "BC": "British Columbia",
          "MB": "Manitoba",
          "NB": "New Brunswick",
          "NL": "Newfoundland and Labrador",
          "NT": "Northwest Territories",
          "NS": "Nova Scotia",
          "NU": "Nunavut",
          "ON": "Ontario",
          "PE": "Prince Edward Island",
          "QC": "Quebec",
          "SK": "Saskatchewan",
          "YT": "Yukon Territory"
        }
      }
    ]
  }
]

We would return something like

{
        "code": "CA",
        "name": "Canada",
        "states": {
          "AB": "Alberta",
          "BC": "British Columbia",
          "MB": "Manitoba",
          "NB": "New Brunswick",
          "NL": "Newfoundland and Labrador",
          "NT": "Northwest Territories",
          "NS": "Nova Scotia",
          "NU": "Nunavut",
          "ON": "Ontario",
          "PE": "Prince Edward Island",
          "QC": "Quebec",
          "SK": "Saskatchewan",
          "YT": "Yukon Territory"
        }
}

When requesting something like https://:site/wp-json/wc/v2/data/locations/NA, the whole object should not be wrapped in an array like it is now:

[
  {
    "code": "NA",
    "name": "North America",
    ...
  }
]

(Same issue in the CA response above too).

ryelle · 2017-05-19T22:19:58Z

How would changing the response like that affect the schema? I can see removing the array wrapper for continent & country responses, because we know we're only requesting one item, and that wouldn't affect the schema as it is now.

(Honestly I'm not sure I see the relationship of schema for this data, since we're not updating anything on this endpoint)

claudiosanches · 2017-05-19T22:41:15Z

Honestly I'm not sure I see the relationship of schema for this data, since we're not updating anything on this endpoint

Maybe better write first the schema, since it will make easy to code the data that should return.

mikejolley · 2017-05-22T13:39:28Z

@justinshreve Good point from @ryelle ^ #15162 (comment)

If the schema differs based on the input, how do you represent that in the response? To have 2 different schemas you'd need /country/ /continent/? Which I think brings this full circle 😱

Unless the schema was abstracted somewhat?

code - Code of that requested
name - Name of that requested
locations (?) - List of state or country codes depending on what was requested.

Then it applies to both?

Let's discuss before making further changes so we have a solution.

emdashcodes · 2017-05-22T15:04:27Z

Yeah good point about the schema @ryelle & @mikejolley.

I like your suggestion Mike. I think returning code, name, and an array of locations makes sense.

ryelle · 2017-05-22T15:08:45Z

So with the abstracted schema, would /<continent> still include the nested { code, name, list of states } in each country on that continent?

emdashcodes · 2017-05-22T15:25:32Z

Yeah I think we can/should still do that.

mikejolley · 2017-05-22T15:26:58Z

@justinshreve How is that represented in schema? Does that mean locations have to be objects too? What props?

emdashcodes · 2017-05-22T15:30:54Z

Wouldn't it just be similar to what it is now, following the schema updates?

  {
    "code": "NA",
    "name": "North America",
    "locations": [
        {
           "code": "US",
           "name": "United States (US)",
           "locations": [
            {
               "code": "AL",
               "name": "Alabama",
            ...

emdashcodes · 2017-05-22T15:31:22Z

Then if you requested /US, the country part would drop off.

mikejolley · 2017-05-22T15:41:00Z

Ah I get you. @ryelle can that be represented in the schema without issue?

ryelle · 2017-05-22T18:27:44Z

These latest changes updates the response object based on what filter is passed in (country, continent, or none). I've also tried to update the schema to reflect that the items at different levels may be countries, continents, states, or absent (it makes more sense if you look at the schema and some response objects).

claudiosanches · 2017-05-22T23:13:50Z

I could imagine this with some other endpoints, like:

All results:

GET /data/locations

[
  {
    "code": "AF",
    "name": "Africa",
    "countries": [...],
    "_links": {
      "self": [
        {
          "href": "https://example.com/wp-json/wc/v2/data/locations/af"
        }
      ],
      "collection": [
        {
          "href": "https://example.com/wp-json/wc/v2/data/locations"
        }
      ]
    }
  },
  {
    "code": "AN",
    "name": "Antarctica",
    "countries": [...],
    "_links": {
      "self": [
        {
          "href": "https://example.com/wp-json/wc/v2/data/locations/an"
        }
      ],
      "collection": [
        {
          "href": "https://example.com/wp-json/wc/v2/data/locations"
        }
      ]
    }
  },
  ...
]

Specific continent:

GET /data/locations/af

{
  "code": "AF",
  "name": "Africa",
  "countries": [...],
  "_links": {
    "self": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/af"
      }
    ],
    "collection": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations"
      }
    ]
  }
}

Specific country:

GET /data/locations/af/za

{
  "code": "ZA",
  "name": "South Africa",
  "states": [
    {
      "code": "EC",
      "name": "Eastern Cape"
    },
    {
      "code": "FS",
      "name": "Free State"
    },
    {
      "code": "GP",
      "name": "Gauteng"
    },
    {
      "code": "KZN",
      "name": "KwaZulu-Natal"
    },
    {
      "code": "LP",
      "name": "Limpopo"
    },
    {
      "code": "MP",
      "name": "Mpumalanga"
    },
    {
      "code": "NC",
      "name": "Northern Cape"
    },
    {
      "code": "NW",
      "name": "North West"
    },
    {
      "code": "WC",
      "name": "Western Cape"
    }
  ],
  "_links": {
    "self": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/af/za"
      }
    ],
    "up": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/af"
      }
    ]
  }
}

This should require a class for data/locations and data/locations/af, and another class for data/locations/af/za, as well two different schema too.

But your currently schema is correct and we can go with it.
Just need to do some styling fixes, like use period in the schema and docs, like we does for the other endpoints.

ryelle · 2017-05-23T14:39:44Z

I dropped the /locations/<continent>/<country> based on this comment #15162 (comment) about real use-cases, so I'm going to leave the endpoints as-is.

I've added periods to all returned doc strings, and I think I've addressed all the code & doc style feedback.

emdashcodes

Did another pass over the code. Tests pass. Responses look good.

I don't have anything else to add here. LGTM!

mikejolley · 2017-05-24T09:54:13Z

First off @ryelle, really sorry for going backwards and forwards on this. I appreciate the work you're doing here and acknowledge we're lacking good guidelines for new endpoints and I'm trying to rectify that this week.

The schema of this is bothering me, in particular this part:

List of locations in this country (absent if state).

I feel we may just be trying to do too much in that one endpoint.

Going back to @claudiosanches comment above (#15162 (comment)) whilst we should definitely not add the nesting back for continents (because it would be hard to consume) we could make a minor change here and have 2 separate endpoints.

So this structure:

data/locations/countries/
- data/locations/countries/gb
- data/locations/countries/us
- ...
data/locations/continents/
- data/locations/continents/eu
- data/locations/continents/na
- ...

data/locations will just list resources like your data endpoint.

So a specific continent looks like:

{
  "code": "EU",
  "name": "Europe",
  "countries": [...],
  "_links": {
    "self": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/continents/af"
      }
    ],
    "collection": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/continents"
      }
    ]
  }
}

And a specific country looks like:

{
  "code": "ZA",
  "name": "South Africa",
  "states": [
    {
      "code": "EC",
      "name": "Eastern Cape"
    },
    {
      "code": "FS",
      "name": "Free State"
    },
    {
      "code": "GP",
      "name": "Gauteng"
    },
    {
      "code": "KZN",
      "name": "KwaZulu-Natal"
    },
    {
      "code": "LP",
      "name": "Limpopo"
    },
    {
      "code": "MP",
      "name": "Mpumalanga"
    },
    {
      "code": "NC",
      "name": "Northern Cape"
    },
    {
      "code": "NW",
      "name": "North West"
    },
    {
      "code": "WC",
      "name": "Western Cape"
    }
  ],
  "_links": {
    "self": [
      {
        "href": "https://example.com/wp-json/wc/v2/data/locations/countries/za"
      }
    ]
  }
}

Does that sound acceptable? @claudiosanches

I'll be talking to Todd and @mattyza later about what version these endpoints can realistically go in, since we're going to need to version bump the API for discovery. With that in mind, if you could add a feature/rest-api-v3 branch and target that instead of master we'll be able to approve and merge this until a decision is made.

cc @justinshreve

claudiosanches · 2017-05-24T09:58:36Z

@mikejolley sounds good.

Countries inside the data/locations/continents could even not return any extra information, maybe only codes and paths to help query in the data/locations/continents/ISO-CODE` endpoint.

ryelle · 2017-05-24T17:11:18Z

Added a new branch feature/rest-api-v3 and retargeted this one for that branch. I also switched the endpoints to /data/countries & /data/continents, updated the schema, tests, & documentation to reflect that, and added relation links to all responses.

claudiosanches · 2017-05-24T20:57:30Z

@ryelle still missing handle each single item as an individual result, so you'll be able to set _links as @mikejolley described.
Check our other REST API classes, there we have get_item() and get_items() to solve it.

…ntation

…t_* helper function. This also adds the `_links` data to each item in the collection.

mikejolley · 2017-05-29T09:47:56Z

@claudiosanches Can you be a little more detailed? What is missing? Is it there now?

claudiosanches · 2017-05-29T16:51:49Z

@mikejolley Kelly already fixed it, but I was talking about treating each element as an element in individual, so including _links with self and collection.

claudiosanches · 2017-05-29T16:52:57Z

includes/api/class-wc-rest-data-continents-controller.php

+		 * @param array            $data     The original list of continent(s), countries, and states.
+		 * @param WP_REST_Request  $request  Request used to generate the response.
+		 */
+		return apply_filters( 'woocommerce_rest_prepare_data_continent', $response, $continent, $request );


This filter should be included into prepare_item_for_response.

claudiosanches · 2017-05-29T16:54:47Z

includes/api/class-wc-rest-data-continents-controller.php

+		}
+
+		$continent['countries'] = $local_countries;
+		$response = $this->prepare_item_for_response( $continent, $request );


$response = $this->prepare_item_for_response( $continent, $request ); $response = $this->prepare_response_for_collection( $response );

Both lines should be part of get_item and get_items and not while getting the "row data".

claudiosanches · 2017-05-29T16:55:28Z

includes/api/class-wc-rest-data-continents-controller.php

+		if ( ! is_wp_error( $item ) ) {
+			$response->add_links( $this->prepare_links( $item ) );
+		}
+		return $response;


Missing woocommerce_rest_prepare_* filter.

claudiosanches · 2017-05-29T16:57:11Z

includes/api/class-wc-rest-data-countries-controller.php

+			}
+		}
+		$country['states'] = $local_states;
+		$response = $this->prepare_item_for_response( $country, $request );


Need the same change here, putting both into get_item and get_items.

claudiosanches · 2017-05-29T16:58:59Z

includes/api/class-wc-rest-data-countries-controller.php

+	public function prepare_item_for_response( $item, $request ) {
+		$response = rest_ensure_response( $item );
+		$response->add_links( $this->prepare_links( $item ) );
+		return $response;


Missing woocommerce_rest_prepare_* filter.

claudiosanches · 2017-05-29T17:00:30Z

includes/api/class-wc-rest-data-controller.php

+
+		// Wrap the data in a response object.
+		$response = rest_ensure_response( $data );
+		$response->add_links( array(


This class should have a prepare_links method like all other classes in our REST API.

claudiosanches · 2017-05-29T17:01:16Z

includes/api/class-wc-rest-data-continents-controller.php

+	 */
+	protected function prepare_links( $item ) {
+		$links = array();
+		if ( array_key_exists( 'code', $item ) ) {


Not sure if need to check for array_key_exists( 'code', $item ) since now all items should have self and collection.

claudiosanches · 2017-05-30T20:53:11Z

includes/api/class-wc-rest-data-continents-controller.php

+	public function get_item( $request ) {
+		$data = $this->get_continent( strtoupper( $request['location'] ), $request );
+		if ( empty( $data ) ) {
+			$data = new WP_Error( 'woocommerce_rest_data_invalid_location', __( 'There are no locations matching these parameters.', 'woocommerce' ), array( 'status' => 404 ) );


No need to pass WP_Error to variables, you can just use return and stop the code here.
This will avoid the need to check for is_wp_error in prepare_item_for_response too.

claudiosanches · 2017-05-30T20:56:32Z

includes/api/class-wc-rest-data-continents-controller.php

+	 * @return WP_REST_Response $response Response data.
+	 */
+	public function prepare_item_for_response( $item, $request ) {
+		$response = rest_ensure_response( $item );


Can change it to:

$data = $this->add_additional_fields_to_object( $item, $request ); $data = $this->filter_response_by_context( $data, 'view' ); $response = rest_ensure_response( $data ); $response->add_links( $this->prepare_links( $item ) );

add_additional_fields_to_object will allow extend results using register_rest_field.

mikejolley · 2017-05-31T09:50:21Z

@justinshreve When those last items are done, are you going to cherry-pick this into the wc-api-dev repo?

…ster_rest_field`

emdashcodes · 2017-05-31T16:39:15Z

@mikejolley Yeah, I can get these into the plugin.

Are we good to go?

claudiosanches

Looks good, great work :)

emdashcodes · 2017-05-31T20:45:31Z

Merged into the feature plugin over at woocommerce/wc-api-dev#3. Thanks @ryelle!

I think we can close this, since we are not going to be using the v3 branch.

ryelle added Focus: API labels May 18, 2017

ryelle self-assigned this May 18, 2017

ryelle requested review from claudiosanches and mikejolley May 18, 2017 21:44

claudiosanches suggested changes May 18, 2017

View reviewed changes

mikejolley requested changes May 19, 2017

View reviewed changes

emdashcodes requested changes May 19, 2017

View reviewed changes

ryelle force-pushed the add/endpoint-data-locations branch from cb5e494 to 22a9c70 Compare May 19, 2017 18:22

mikejolley mentioned this pull request May 23, 2017

REST API v3 #15235

Closed

6 tasks

mikejolley modified the milestone: 3.1.0 May 23, 2017

emdashcodes approved these changes May 23, 2017

View reviewed changes

ryelle force-pushed the add/endpoint-data-locations branch from 9dfe840 to 1607338 Compare May 24, 2017 17:10

mikejolley removed this from the 3.1.0 milestone May 24, 2017

Update location -> continents/countries in keys, filter names, docume…

1f81464

…ntation

ryelle force-pushed the add/endpoint-data-locations branch from 1607338 to 1f81464 Compare May 25, 2017 14:57

Refactor to use get_item for single continents/countries, with a ge…

5efa549

…t_* helper function. This also adds the `_links` data to each item in the collection.

claudiosanches reviewed May 29, 2017

View reviewed changes

Move item-prepare code into the prepare method

4ae89e0

claudiosanches reviewed May 30, 2017

View reviewed changes

mikejolley added needs: author feedback The issue/PR needs a response from any of the parties involved in the issue. and removed Status: Needs Review labels May 31, 2017

Return wp_error directly, and allow for extending endpoints via `regi…

d462829

…ster_rest_field`

claudiosanches approved these changes May 31, 2017

View reviewed changes

emdashcodes pushed a commit to woocommerce/wc-api-dev that referenced this pull request May 31, 2017

Adds location data endpoints. Reviewed in woocommerce/woocommerce#15162

1c4e22f

emdashcodes mentioned this pull request May 31, 2017

Add location data endpoints woocommerce/wc-api-dev#3

Merged

emdashcodes closed this May 31, 2017

claudiosanches deleted the add/endpoint-data-locations branch July 3, 2017 15:54

API: Add endpoint for fetching location data #15162

API: Add endpoint for fetching location data #15162

Uh oh!

Conversation

ryelle commented May 18, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

claudiosanches left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mikejolley left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryelle commented May 19, 2017

Uh oh!

emdashcodes left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

emdashcodes commented May 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ryelle commented May 19, 2017

Uh oh!

claudiosanches commented May 19, 2017

Uh oh!

mikejolley commented May 22, 2017

Uh oh!

emdashcodes commented May 22, 2017

Uh oh!

ryelle commented May 22, 2017

ryelle commented May 18, 2017 •

edited

Loading

emdashcodes commented May 19, 2017 •

edited

Loading

claudiosanches commented May 22, 2017 •

edited

Loading