1. Handicap Market Sorting should work like this

a. when i select to Sort by Line Value

• Sort handicap markets numerically by their line values.
  Example: -2.5, -1.5, +0.5, +1.5, etc.

b. when i select to Sort by Probability (Fix Required)

• Current implementation fails for handicap markets as it uses over probability or average values.

• Instead, use the Player 1 probability for the negative handicap line.

• Sort based on absolute closeness to 50 percent, calculated as abs(probability - 50).

---

2. Live UI Update on markets_priced Notification

Current Problem

• When a markets_priced notification is received via PubSub:

  • The backend updates the MarketStore.
  • However, the UI does not update dynamically.
  • A full page refresh is required to see the updated odds.

Expected Behavior

• The PubSub listener should:

  • Be active at all times, listening to the markets_priced channel.
  • On receiving a notification with matchId, immediately query all markets for that match (even if not selected).

If the match is selected on the Markets Page:

• Compare newly fetched odds with the previously stored ones.

• For each updated price:

  • If the price increased, show a small green up arrow beside the odds.
  • If the price decreased, show a small red down arrow beside the odds.
  • These indicators should automatically disappear after 2 seconds.

• All updates should happen dynamically, without requiring a page reload.

---

Action Items

• Fix sorting logic for handicap markets to use Player 1's probability on the negative line.
• Ensure PubSub properly fetches updated markets on notification.
• If the match is selected, compare odds and update the UI with indicators.
• Indicators should display for 2 seconds to show price movements.
• Ensure the UI updates in real time without needing a page refresh.

why do we need to subscribe in use-markets, if listener is always active, there is no need to subscribe

this is what should happen,

listener is active

notify come of markets_priced,

we fetch all the markets for that match, regardless of fact that the match is selected or not

there is no need to store all the markets at once

this is the flow

we go to markets page ,

we select a market,

after its selection, we send query to get all markets for that match,

we get all the markets and display the markets

now for a selected match, if markets are updated, we will receive a notification, we will then on the spot, dynamically update the market prices, without needing to full refresh the page , and show indicators according to update of prices , updating the market

we do not need market-store, delete that , we do not need to store all the markets

now if selected a match, and its markets are not fully generated yet, it will show no markets found which is correct, but as soon as we receive notification, we will give query to fetch all markets for that match , we will then on the spot, dynamically update the market prices, without needing to full refresh the page , updating the market

this is how notification is sent from the backend

public async Task PublishMarketsPriced(long matchId)
{
var json = JsonSerializer.Serialize(matchId);

  using var conn = new NpgsqlConnection(_connectionString);  
  await conn.OpenAsync();  

  using var cmd = new NpgsqlCommand(  
      $"NOTIFY markets_priced, '{json.Replace("'", "''")}';",  
      conn  
  );  

  await cmd.ExecuteNonQueryAsync();  

}