Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration: location based rule tests #71

Closed
rowanseymour opened this issue Jul 27, 2017 · 3 comments
Closed

Migration: location based rule tests #71

rowanseymour opened this issue Jul 27, 2017 · 3 comments

Comments

@rowanseymour
Copy link
Member

rowanseymour commented Jul 27, 2017

HasWard
HasDistrict
HasState

We probably don't want to send all adminboundary information with every request, so need a solution that either caches this, calls back to the caller, or accesses an external service.

@nicpottier
Copy link
Collaborator

Assets with lazy loading?

@rowanseymour
Copy link
Member Author

I think we agree now this should be handled via a generic asset caching system, so the question is what kind of asset is it. Doesn't make much sense to model each location as a separate asset, so I think it's something that describes all the admin boundaries for a country together, e.g.

"assets": [
  {
    "type": "boundary_set",
    "content": {
      "states": [
         {
           "name": "Kigali",
           "districts": [
             {
               "name": "Gasabo",
               "wards": [...]
             },
             ...
           ]
         },
         ...
      ]
    }
  }
]

@rowanseymour
Copy link
Member Author

Added in #115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants