bug: sanctions panel ignores timeRange filter — newEntryCount always 0

[rayanhabib07]

Variant

worldmonitor.app (Full / Geopolitical)

Affected area

Market Radar / Crypto

Bug description

Summary

The sanctions pressure panel does not pass the timeRange parameter to the API, causing all time-sensitive metrics to be incorrect.

Bug

The URL contains timeRange=7d but the API call is:

/api/sanctions/v1/list-sanctions-pressure?max_items=30

No timeRange param is passed. As a result:

• newEntryCount is always 0 because it compares against the dataset date (March 27) instead of the user's selected window
• Vessels, aircraft, and countries counts also ignore the timeRange filter

Environment

• Tested on worldmonitor.app

Steps to reproduce

Steps to Reproduce

1. Open the sanctions panel
2. Set timeRange to 7d
3. Observe "New: 0" despite entries existing within that window
4. Inspect the network request — no timeRange param in the API call

Expected behavior

The API call should include the timeRange parameter and newEntryCount should reflect entries added within the selected window.

Screenshots / Console errors

No response

Browser & OS

Chrome 120 OS.

[rayanhabib07]

@koala73
What external API should power this endpoint (OFAC, EU, UN)?
What fields should the response include beyond newEntryCount?
Where does the SanctionsPanel live in the UI?
How should timeRange filter the data?

[koala73]

timeRange filter concept is deferred
It's applicable to certain things easily - but it's hard for everything - like Sanctions, but many other
Requires storing in DB a ton of things - currrently low value

[SebastienMelki]

@koala73 confirmed on Mar 28 that timeRange filtering for the sanctions panel is intentionally deferred — implementing it correctly requires storing historical sanctions data in the DB. Suggesting we close this as "deferred by design."

One UX improvement: the timeRange UI element in the sanctions panel should ideally be hidden or disabled until server-side filtering is supported, to avoid confusion.

@koala73 — OK to close?