Skip to content

Chore: assert membership where a combination promises no order - #862

Merged
zachdaniel merged 2 commits into
ash-project:mainfrom
matt-beanland:chore/assert-membership-where-a-combination-promises-no-order
Sep 21, 2026
Merged

zachdaniel merged 2 commits into
ash-project:mainfrom
matt-beanland:chore/assert-membership-where-a-combination-promises-no-order

Conversation

@matt-beanland

Copy link
Copy Markdown
Contributor

Contributor checklist

  • I accept the AI Policy, or AI was not used in the creation of this PR.
  • Bug fixes include regression tests
  • Chores
  • Documentation changes
  • Features include unit/acceptance tests
  • Refactoring
  • Update dependencies

Summary

Two commits:

one fixes a flake in a combination test that assumed an ordering the query doesn't guarantee. The sibling test that does sort is unchanged.

other commit runs the formatter onuniq_aggregate_sort_test.exs

Testing

1001/1004 before and after. There failures are inherited/ash_sql related.

mix format --check-formatted fails on main without it.
`first_and_last_post` sorts and limits within each branch and the outer query
does not sort, so which of the two rows comes back first is undefined. The
assertion named an order, and it named neither the branch order nor the one
the base branch selects, so it failed intermittently under the full suite.

`with data and sort` covers the ordered case.
@zachdaniel
zachdaniel merged commit 08bd509 into ash-project:main Sep 21, 2026
111 of 126 checks passed
@zachdaniel

Copy link
Copy Markdown
Contributor

🚀 Thank you for your contribution! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants