Skip to content

Conversation

@TaylorWatson
Copy link
Member

Summary

  • retarget the component library to net9.0, enable nullable/implicit usings, and update the package metadata and dependencies
  • ensure the list template supports Blazor's interactive auto render mode and safely handles empty item collections
  • refresh the documentation and imports to highlight the new .NET 9 support

Testing

  • not run (dotnet CLI is unavailable in the execution environment)

https://chatgpt.com/codex/tasks/task_e_68e704dd3670833295d6e601c6296719

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

Comment on lines 1 to +2
@namespace TailBlazor.List
@attribute [RenderModeInteractiveAuto]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove unconditional RenderModeInteractiveAuto attribute

Applying @attribute [RenderModeInteractiveAuto] in the component library forces every consuming app to configure Blazor’s interactive auto render mode. Existing Blazor Server/WebAssembly apps that simply reference this component but have not registered interactive auto services will now throw InvalidOperationException at runtime because the render mode is unsupported. The list component previously worked in any app; after this change it crashes unless the host uses SSR with interactive auto. Consider leaving render mode decisions to the host or making this opt‑in so the package remains compatible with non‑SSR projects.

Useful? React with 👍 / 👎.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant