Dan Feder

Try switching from select2 to tagify in JSON form

6

Select2 isn't compatible with the last version of Drupal. We've been using select2 for a long time but the underlying library is mostly abandoned. There has been no release for...

Rename harvest and datastore to dkan_harvest and dkan_datastore

1

These generic names were a bad call. Let's rip off the bandaid and rename them under a dkan_prefix as they are submodules and only (for now) relevant to DKAN. ##...

Now that the DKAN-specific stuff is in the form widget plugin, move this plugin from the json_form_widget module into DKAN itself.

We have a WidgetRouter in JSON Form Widget that has gotten a bit unwieldy. It is not exactly a router it is also a collection of methods that all transform...

Improvements to OpenAPI spec [meta-issue]

2

This is a stub that needs to be broken out into a few specific tickets. Some possible improvements to our spec: 1. Look at the output of https://pb33f.io/doctor/ report on...

Simplify harvest storage and stop using contracts interfaces

1

The havest module uses the contracts storage interfaces which result in a lot of unnecessary abstractions. We have a bunch of different "stores" (items, hashes etc) that all require their...

Break JSON Form Element/Widget off into standalone module

3

JSON form widget can and should stand on its own as a Drupal self-contained module. This will allow others to use and contribute to this powerful functionality that has potential...

We have a single generic Event class in DKAN shared everywhere, this doesn't make a lot of sense. Event classes specific to the specific event they're for make a lot...

In NodeWrapper/Data there are these two concepts that don't make a lot of sense and appear to just be workarounds. Can we factor these out and make this stuff cleaner?

This was an experiment to see how viable it would be to move from CodeClimate to qlty.sh, which is going to replace it.