data-driven

• A remediation sequence gets triggered using:

{
  "data": {
    "labels": {
      "Problem URL": "https:///#problems/problemdetails;pid=-240816790436828345_1633506659151V2"
    },
    "problem": {
      "ProblemTitle": "Http monitor global outage",
    },
    "project": "musicshop",
    "service": "carts",
    "stage": "production"
  },
  "id": "d485ea90-e1ef-4ce2-af21-32

Swagger feature docstring (and spec?) places tags on route-data root:

https://github.com/metosin/reitit/blob/master/modules/reitit-swagger/src/reitit/swagger.cljc#L55

Examples place tags key under swagger:

https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj#L30

Both seem to generate proper swagger.json, but first one fails spec validation. Why? Sp

The Generated Client API is remains largely undocumented...

It would also be awesome if we could include the documentation of the API in the Generated DSL

We should add a list of all methods of a class in the documentation.

Currently the model namespace keeps track of registered models and creates maps for "quick" mapping (e.g. mapping a model field to table column). This is mainly for performance benefits.

https://github.com/kwrooijen/gungnir/blob/54fa3b8083c21d52e3c2990ef04cf4a63a1ad8b9/src/cljc/gungnir/model.cljc#L12-L17

These maps are stored in atoms. However it might be nice to actually store then in `^:dy

It should be rather trivial to replace most of the legacy jQuery-based code in jquery.js with an IXSL (Saxon-JS) implementation.

We need to keep the fetchDispatchXML function though.