Skip to content

docs: add the roadmap for 5.4.0 and the 6.0 family #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CaffeinatedCoder merged 1 commit into from
Sep 19, 2026
Merged

docs: add the roadmap for 5.4.0 and the 6.0 family #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,11 @@ them with no base to resolve against, so **every link in them must be an absolut
are condensed on purpose and will overlap `docs/` — that duplication is the price of a package page
that stands alone, and `DocumentationLinkTests` guards only the part that fails silently.

`ROADMAP.md` at the root is the plan for 5.4.0 and the 6.0 family: the delete guard, the generic
descriptor differ, the rename under the `CodoMetis.` prefix, the plugin host and EF Core 11. It sits at the
root on purpose: `DocumentationLinkTests` checks its links, but `DocumentationApiTests` scans only
`docs/`, so the roadmap may name methods that do not exist yet.

### How it works end-to-end

1. **Fluent API** (`ComplexIndexExtensions.cs`) — User calls `.HasComplexIndex(...)` or `.HasComplexCompositeIndex(x => new { x.Prop, x.Complex.Nested })` in `OnModelCreating`. These methods store all index metadata as EF Core annotations on the property or entity.
Expand Down
Loading
Loading