[refactor] Standardize agent name fallback handling and improve null safety #292
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
fallbackAgentName
constant to centralize default agent namingAgentNameProvider
to properly handle null valuesWhy
We needed to improve the consistency and maintainability of agent name handling across the application. The previous implementation had:
This refactor centralizes the fallback logic and makes the codebase more maintainable while properly handling null values in the database schema.