Repository navigation
fix: arrange community author metadata on two lines - #68
Merged
Merged
Conversation
This was referenced Nov 11, 2026
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
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.
Community authors now use two lines: server code, nickname and verified mark on the first; plain activity grade, selected arcana and elapsed time on the second. Missing fields omit their separators, and unverified users retain the existing grade-hiding policy. Post feed/detail and comment/reply DTOs accept the optional arcana field supplied by the coordinated backend changes without per-author requests.
Validation: npm run verify; updated existing post/comment author tests; nine workflow-contract tests; secret scan. Version1.0.26. This PR changes normal community author areas only. Auth/Community arcana projection PRs must be delivered first for populated arcana values; older responses remain compatible. Merge and production deployment are not part of this request.
Coordinated backend PRs: devnogi/devnogi-auth-server#59 · devnogi/devnogi-community-server#212