feat(components/Header): render year dynamically - #925
Merged
AceTheCreator merged 2 commits intoFeb 11, 2026
Conversation
DarshanCode2005
requested review from
AceTheCreator,
Mayaleeeee,
ashmit-coder and
thulieblack
as code owners
February 3, 2026 18:06
✅ Deploy Preview for peaceful-ramanujan-288045 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
@TenzDelek @AceTheCreator quick-win PR. Could you please review this. 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The conference year (2026) was hardcoded in the Header component (
components/Header/header.tsx, line 30).This makes the codebase less reusable for future conference editions and requires manual code changes each year.
Solution
The year has been extracted into a configurable value instead of being hardcoded.
This improves maintainability and makes it easier to reuse the codebase for future AsyncAPI conferences without touching component logic.