Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bind:after not working

Open
#2 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

Start with CompilationService.CompileRazorCodeToBlazorComponentType and compare its compiled component behavior with the Try.MudBlazor app, focusing on the libraries or runtime support involved in bind:after. Reproduce the issue with a component using bind:after and consider the work complete when the event fires for components compiled by the service.

Written by the indexing model from the issue text.

Description

When I test a component in the Try.MudBlazor app and I have a bind:after event configured, that event fires as expected. However, if I use your CompilationService and call CompileRazorCodeToBlazorComponentType that component works for the basic binding, but any bind:after event never fires. Let me know if I'm missing something on my end with a misconfiguration, or if there is some difference in a required library not loading in this tool.

Dominant language
C#
Stars
6
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.