Feature/costing with mapped requests (#227)

* costing with mapped request * handle unknowned widgets
ecmwf-projects · Oct 14, 2024 · fbd531a · fbd531a
1 parent c9f47e5
commit fbd531a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/cads_adaptors/adaptors/cds.py b/cads_adaptors/adaptors/cds.py
@@ -79,16 +79,18 @@ def estimate_costs(self, request: Request, **kwargs: Any) -> dict[str, int]:
         # Safety net, not all stacks have the latest version of the api:
         if "inputs" in request:
             request = request["inputs"]
+        mapped_request = self.apply_mapping(request)
+
         # "precise_size" is a new costing method that is more accurate than "size
         if "precise_size" in costing_config.get(cost_threshold, {}):
             costs["precise_size"] = costing.estimate_precise_size(
                 self.form,
-                request,
+                mapped_request,
                 self.constraints,
                 **costing_kwargs,
             )
         # size is a fast and rough estimate of the number of fields
-        costs["size"] = costing.estimate_number_of_fields(self.form, request)
+        costs["size"] = costing.estimate_number_of_fields(self.form, mapped_request)
         # Safety net for integration tests:
         costs["number_of_fields"] = costs["size"]
         return costs

diff --git a/cads_adaptors/costing.py b/cads_adaptors/costing.py
@@ -7,7 +7,6 @@
 
 EXCLUDED_WIDGETS = [
     "GeographicExtentWidget",
-    "UnknownWidget",
 ]
 
 # TODO: Handle DateRangeWidget