Ticket #972 (closed enhancement: wontfix)
Merge 'extras' into main package dict rather than having separate key
| Reported by: | rgrp | Owned by: | sebbacon |
|---|---|---|---|
| Priority: | major | Milestone: | ckan-v1.5 |
| Component: | ckan | Keywords: | model |
| Cc: | Repository: | ckan | |
| Theme: | none |
Description
Rather than have a separate 'extras' key all the extras fields should be consolidated into the main package dict when presenting the package internally or e.g. via the API.
Why? Extras are really just an artefact of our internal storage model. Clients of the system (both internal and external) should just see a set of key/values with no distinction between extras and non-extras.
Issues
- Possible breaking change to the API (could enforce backwards compatibility by keepings extras for the time being)
Possible subticket of forms refactoring: #961
Change History
comment:2 Changed 3 years ago by thejimmyg
- Repository set to ckan
- Status changed from new to closed
- Theme set to none
- Resolution set to wontfix
Having thought about this more David Raznick and I have decided to stick with separate extras for the timebeing. Mainly because of internationalisation issues.
Note: See
TracTickets for help on using
tickets.
I don't really agree with this. In fact I'd rather move further away from auto-magic key value pairs stored in JsonTypes?. Can we discuss on Skype please?