feat: add KnowledgeLevelId and JobSectorId to content entities#63
Merged
Rashed99Azm merged 1 commit intoJun 16, 2026
Merged
Conversation
- Add KnowledgeLevelId/JobSectorId (Guid?) to News, Event, Resource domain entities, factory methods, UpdateContent methods, and EF configs - Add migration AddContentInterestTopicLinks - Add fields to ContentBody DTOs, CountryContentRequest flow - Add Resource.Center.View permission - Add filtering/sorting to public listing endpoints with auto-detect - Add fields to admin create/edit commands, handlers, and endpoints - Fix PublicNewsDto/PublicEventDto/PublicResourceDto in GetById handlers - Fix UserMutationTests TopicId -> InterestTopicId
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.
Summary
Adds
KnowledgeLevelIdandJobSectorId(nullableGuid?) to content entities (News, Events, Resources) to enable interest-based sorting and filtering. Both fields referenceInterestTopicentries with categories"knowledge_assessment"and"job_sector".Changes
Domain & Data
KnowledgeLevelId/JobSectorIdtoNews,Event,ResourceentitiesUpdateContentmethods20260614113707_AddContentInterestTopicLinksPublic API — Listing Endpoints
KnowledgeLevelId/JobSectorIdquery params to 3 public listing endpointsAdmin API — Create/Edit
Country Content Request Flow
SubmitCountryContentRequestCommandHandlerCountryContentRequestDtoand mapperCountryContentRequestApprovedContentHandlerPermissions
Resource.Center.Viewtopermissions.yamlPermissionsYamlSchemaTestscount (57 → 58)Fixes
PublicNewsDto/PublicEventDto/PublicResourceDtoconstruction in GetById handlersUserMutationTests— renameTopicIdtoInterestTopicId