Skip to content

Added ItemsProvider to BbDataView. Added example in demo page.#306

Open
djb-fnz wants to merge 27 commits into
blazorblueprintui:developfrom
djb-fnz:feature/data-view-items-provider
Open

Added ItemsProvider to BbDataView. Added example in demo page.#306
djb-fnz wants to merge 27 commits into
blazorblueprintui:developfrom
djb-fnz:feature/data-view-items-provider

Conversation

@djb-fnz
Copy link
Copy Markdown
Contributor

@djb-fnz djb-fnz commented Apr 21, 2026

Description

  • Added ItemsProvider to BbDataView to provided server-side data loading similar to BbDataGrid.
  • Added an example of using ItemsProvider to the BbDataView demo page.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)

Testing Checklist

  • Blazor Server
  • Blazor WebAssembly
  • Blazor Hybrid (MAUI)
  • Keyboard navigation / accessibility
  • Dark mode

mathewtaylor and others added 25 commits March 6, 2026 13:38
release: Primitives v3.4.0 + Components v3.4.0
release: Primitives v3.5.0 + Components v3.5.0
release: Primitives v3.6.0 + Components v3.6.0
…ssue-fix

Fix sortable.js casing, for linux deployments
release: Primitives v3.6.1 + Components v3.6.1
release: Primitives v3.7.1 + Components v3.7.1
release: Primitives v3.7.2 + Components v3.7.2
release: Primitives v3.9.1 + Components v3.9.1
release: Primitives v3.9.3 + Components v3.9.3
Had to add this to my imports to get MainLayout to pickup `BpPortalHost`
Update README with out of box working missing code
fix: update source property from Avatar component
@mathewtaylor
Copy link
Copy Markdown
Contributor

mathewtaylor commented May 2, 2026

Hey @djb-fnz, really nice work on this one! The implementation closely mirrors the existing DataGridItemsProvider pattern, the cancellation handling is solid (CTS swap with OperationCanceledException swallowed in the superseded request), and the demo with Task.Delay realistically exercises the flow. Build is clean and all 67 tests pass locally on this branch.

A couple of small things to sort before we merge:


1. Base branch should be develop, not main

All PRs target develop in this repo. main only gets updated when we cut a release. Could you retarget the base branch on this PR to develop please? Should be a one-click change in the GitHub UI under "Edit" next to the title.


2. Issue #305 referenced in the description doesn't exist

The PR body mentions "Resolves #305" but there's no issue or PR with that number in the repo. Could you either remove the reference or point it to the correct one if you had something specific in mind?


3. Heads up on the unrelated StateHasChanged() in RegisterField

Just noticed RegisterField now calls StateHasChanged() (line 436). I think this is a sensible fix for late-registered fields and I'm happy to keep it. Just wanted to flag that it's outside the ItemsProvider scope so it doesn't get missed in the release notes. No change needed from you.


Once the base branch is retargeted and the #305 reference is sorted we should be good to go. Genuinely great addition to the library, thanks for the contribution!

Thanks, Mathew

release: Primitives v3.10.0 + Components v3.10.0
@djb-fnz djb-fnz changed the base branch from main to develop May 7, 2026 11:48
@djb-fnz
Copy link
Copy Markdown
Contributor Author

djb-fnz commented May 7, 2026

Hi @mathewtaylor. I've completed all the requested changed; this PR now targets the develop base branch and I've removed the orphan reference.

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.

5 participants