Skip to content

AutoMapper/AutoMapper.Extensions.OData

View on GitHub ↗Related repositories →

Creates LINQ expressions from ODataQueryOptions and executes the query.

active 2025-01-042026-04-01 (UTC)

Partial coverage12,300 / 14,005 hourly files (88%) · 2 absent upstream · 1,699 failed, retryable2025-01-042026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
88
Pushes
17
Pull requests
12
Issues
9
Stars
5
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 453 days from 2025-01-04 to 2026-04-01. Pushes: 17 total, peak 4 in a day. Pull requests: 12 total, peak 4 in a day. Issues: 9 total, peak 2 in a day. Comments: 23 total, peak 6 in a day. Stars: 5 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
BlaiseD45171010
joeyadams-bec6014
dotnet-policy-service[bot]4004
AmirEmilV2011
Zamberetta2001
hurcane1001
ramiabughazaleh1001
gmejias-RMS1001

Recent activity

Latest issues, pull requests and releases

  • Issue#246BlaiseD2025-11-21 18:12
    Using GetQueryAsync with filter odata query, AutoMapper doesn’t use mapping parameters (e.g., userid) when translating the filter expression
  • Issue comment#247dotnet-policy-service[bot]2025-11-16 12:52
    Feature: Add ApplyFilterAfterProjection option to control OData filter timing
  • Pull request#247AmirEmilV2025-11-16 12:50
  • Issue comment#246AmirEmilV2025-11-07 19:20
    Using GetQueryAsync with filter odata query, AutoMapper doesn’t use mapping parameters (e.g., userid) when translating the filter expression
  • Issue comment#246BlaiseD2025-11-07 19:14
    Using GetQueryAsync with filter odata query, AutoMapper doesn’t use mapping parameters (e.g., userid) when translating the filter expression
  • Issue comment#245ramiabughazaleh2025-10-24 10:09
    Feature Request: Support for OData Function $apply with Aggregations and GroupBy
  • ReleaseBlaiseD2025-07-12 15:16
    Release 8.0.0
  • Pull request#244BlaiseD2025-07-12 15:09
  • ReleaseBlaiseD2025-07-04 09:51
    Release 7.0.3
  • Issue comment#209hurcane2025-06-05 13:47
    error requesting $count
  • Issue#242BlaiseD2025-05-31 14:40
    Exception expanding dictionaries in complex types
  • Pull request#243BlaiseD2025-05-31 14:32
  • Pull request#243BlaiseD2025-05-31 14:22
  • Issue#242BlaiseD2025-05-31 13:49
    Exception expanding dictionaries in complex types
  • Issue comment#241Zamberetta2025-05-18 21:31
    Unable to auto-expand properties without [EnableQuery]
  • Issue#241Zamberetta2025-05-11 19:00
    Unable to auto-expand properties without [EnableQuery]
  • Issue comment#240BlaiseD2025-05-10 15:23
    Default expansion of dictionaries supported
  • Issue comment#239gmejias-RMS2025-05-02 17:11
    DefaultExpansionsBuilder does not support dictionaries
  • Issue comment#229BlaiseD2025-04-19 14:20
    Expanding complex types by default.
  • Pull request#238BlaiseD2025-04-19 13:48
  • Issue comment#238BlaiseD2025-04-19 13:48
    Expose EnsureStableOrdering property in ODataSettings object
  • Issue comment#238BlaiseD2025-04-12 16:00
    Expose EnsureStableOrdering property in ODataSettings object
  • Issue#235BlaiseD2025-02-15 16:38
    Nested collections are not filtered when they are properties of an entity with a single-valued property or deeper
  • ReleaseBlaiseD2025-02-15 16:38
    Release 7.0.0
  • Pull request#237BlaiseD2025-02-15 16:32

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 5 stars here means stars gained during the window, not the repo's star count.