You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature idea.
Horreum currently uses a different jsonpath dialect for extracting the start and stop in addRunFromData than it does for all the Extractors. This effectively adds cognitive complexity to the user so that Horreum development is easier.
Horreum should provide a consistent means of defining jsonpaths across all features.
The text was updated successfully, but these errors were encountered:
Extract the start and stop using postgresql's dailect by creating a database table where the data can be stored and the extractors can be tested.
Create something to translate between whatever jsonpath dialect we provide users and the various jsonpath dialects that are used within Horreum.
Option 1. is probably the easiest to implement but it maintains the hard dependency on Postgres.
Option 2 is the hardest to implement and honestly the only upside I see is it gives Horreum the ability to transition away from Postgres if needed.
I think options 2 is interesting but it would take a lot longer to implement and the benefit over option 1 is not something Horreum would use in the near term.
Feature idea.
Horreum currently uses a different jsonpath dialect for extracting the start and stop in
addRunFromData
than it does for all the Extractors. This effectively adds cognitive complexity to the user so that Horreum development is easier.Horreum should provide a consistent means of defining jsonpaths across all features.
The text was updated successfully, but these errors were encountered: