chore(sync) Syncing changes from dev to alpha - #731
Open
github-actions[bot] wants to merge 79 commits into
Open
Conversation
chore: flatten frontend root
Applied #363636 backgrounds recursively to definition blocks and pre elements. Removed explicit background inheritance causing invisible text padding blocks. 721
Fixed legacy Detail page headers to contain Badges directly, restored Breadcrumb navigational hierarchies, expanded Details viewing logic thresholds, injected standard button frameworks, and implemented social media verified aesthetics into term list interactions 721
Swapped standard textarea inputs with robust CodeMirror integrations supporting dynamic GFM formats, line-wrapping, and toolbar manipulations imitating the legacy Razor platform 721
add dedicated page routing for creating (/new) and editing (/edit) terms. implement server actions (create, update, delete) to safely handle api data mutations. integrate next.js cache revalidation to ensure instant ui updates after modifications 721
include authenticated API client wrappers, typeScript DTOs, and ui components for term actions, metadata, and related reports. this resolves the frontend typecheck failures caused by uncommitted term references 721
update InteractionEntityType and EntityCardFooterProps to accept 'term' entities. wire up dynamic profile labels and server actions so the footer successfully typechecks and functions within the terms list card 721
Move the CodeMirror dependencies to the main workspace package. Remove the custom toolbar and preview toggle so the markdown field behaves like the old Razor text area. Update technical definitions to use the standard markdown display. 721
Rips out the generic CollectionDetailSection wrappers in favor of a native HTML flow. This explicitly mirrors the Razor _Details.cshtml layout flow line-by-line while retaining Next.js styling 736
Refactors the TermsListCard to mirror the exact header, tight excerpt bounding, and specific dual-column footer found in _Snippet.cshtml, explicitly decoupling it from the generic EntityCardFooter to support custom term tags 736
Feat/issue 721 terms api
test: add api auth coverage and frontend cov gates
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…integration Implements the Next.js routes and UI components for the Initiatives domain, fully replacing the legacy Razor architecture. Adds /initiatives index page and detail view with interactive star, share, and styled linked collection cards. Wires up Create, Edit, and Delete workflows to the new C# backend API 742
… implement sharing/starring.** Fixes list API parsing, resolves edit form data loss with lookup objects, gracefully handles 204 No Content responses, and fully integrates starring and sharing server actions 742
…nd fix test mock Fixes the initiatives test mock, migrates star/share to the global Interactions API, and updates the related payloads and UI 742
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
chore(deps) Update dependency coverlet.collector to v10
chore(deps) Update actions/setup-node action to v7
chore(deps) Update actions/cache action to v6
feat(groups): finalize route migration and api integration (fixes #722)
…timistic state Fix share-modal to send correct recipient with userId and required text field. Fix star toggle in initiative-detail and initiatives-index to revert on error and apply server response on success. #742
…le state handling Add unit tests for the share-modal to verify numeric userId validation and correct payload construction. Add tests for initiative-detail and initiatives-index to ensure the star toggle feature correctly handles optimistic state updates, reverting on API errors and applying server authoritative values on success #742
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ration feat(initiatives): implement Next.js CRUD pages and wire up live API …
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
3 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.
Automated changes by create-pull-request GitHub action