Resource View & DataStore Fields for Loading Objects#229
Conversation
- Load resource views from ckanapi dump.
- Load resource datastore fields from ckanapi dump.
- Update the cli help text.
- Update the cli help text.
- Update the cli help text.
- Update the cli help text.
- Update the cli help text.
- New arg.
- New arg.
- New arg.
|
@wardi okay I believe I have achieved everything here now |
|
Tests can be added by creating mocks for the actions. We should at least cover the happy path and exceptions from each action to make sure they're handled. |
|
Just working on the tests now for this. oh and adding the documentation for expected resource IDs... |
- Test coverage for resource view loading.
- Test coverage for datastore field loading.
- Test coverage for datastore field loading.
|
@wardi okay I think I have covered everything in the new tests now. There were a lot of new things from this, so lots in the tests :/ |
|
TODO: exclude resource id (& package id?) from the resource_view dumpy. And then just use the wrapped resource id for loading. |
- Test coverage for datastore field loading.
|
@wardi as discussed I have popped out the resource_id and package_id from the view dicts. And then just using the parent resource id in the load |
- Test coverage for datastore field loading.
- Test coverage for datastore field loading.
|
This could be improved with support for table designer fields, indexes etc but it's useful so I'll merge it as is. |
wardi
force-pushed
the
feature/resource-options
branch
from
70e9f4f to
f56aca4
Compare
wardi
force-pushed
the
feature/resource-options
branch
from
f56aca4 to
39ca38d
Compare
2 participants
Adds the ability to load the resource_views and datastore_fields from the CKANAPI dump options.
cc: @wardi