Staging#328
Open
jajaramillo24 wants to merge 18 commits into
Open
Conversation
Rename the stage key `mitigate_risks` to `mitigate_risk` across components and the contentTranslation model to keep stage names consistent (editWhatnow.vue, whatnowContentItem.vue, whatnowSummary.vue, store/models/contentTranslation.js). Also add a guard around GoogleAuth initialization in app.js using optional chaining to avoid errors when a Google client_id is not present. Minor whitespace/CSS newline cleanup in whatnowContentItem.vue/whatnowSummary.vue.
Rename mitigate_risks and guard GoogleAuth init
This reverts commit b7a37ec.
Document the new V2 Prepare Messages API and keep legacy V1 WhatNow docs: add detailed V2 endpoints, query params, stage keys and message object structure; update example responses and switch client calls from the legacy whatnow endpoint to /preparemessages. Rename stage key mitigate_risks -> mitigate_risk in examples and add corresponding i18n keys/extras across many locale files. Update scripts to use Cloudflare polyfill CDN, add devServer/HMR options and disable Laravel Mix notifications in webpack.mix.js, and include dependency updates in yarn.lock.
Add V2 PrepareMessages docs, i18n & build updates
joseganora
previously approved these changes
May 28, 2026
Add full-text searching across users.email and user_profiles (first_name, last_name, organisation) with MATCH...AGAINST scoring, and expose a debounced search box in the users list UI. Changes include: request validation for filters.search; UserRepository.applySearchFilter to compute a search_score, filter results and order by relevance; safer profile ordering subquery to ignore deleted profiles and pick the latest profile; a migration to add MySQL FULLTEXT indexes; Vue list page updates (search input, debounce, styles, lifecycle cleanup); store changes to persist searchFilter and include it in API requests while ignoring stale requests; axios interceptor to properly handle cancelled requests; translation entries added for the search label/placeholder across locales; and a feature test asserting admin list sorting by profile last name. These changes improve search relevance and UX for user listing.
This reverts commit f0d7367.
Add full-text searching across users.email and user_profiles (first_name, last_name, organisation) with MATCH...AGAINST scoring, and expose a debounced search box in the users list UI. Changes include: request validation for filters.search; UserRepository.applySearchFilter to compute a search_score, filter results and order by relevance; safer profile ordering subquery to ignore deleted profiles and pick the latest profile; a migration to add MySQL FULLTEXT indexes; Vue list page updates (search input, debounce, styles, lifecycle cleanup); store changes to persist searchFilter and include it in API requests while ignoring stale requests; axios interceptor to properly handle cancelled requests; translation entries added for the search label/placeholder across locales; and a feature test asserting admin list sorting by profile last name. These changes improve search relevance and UX for user listing.
Add full-text user search and search UI
Add disabled support to selectSociety component and wire it from the users filters. Rework users/list filters layout and styling (new utility classes) and disable inputs while fetching. Replace direct search binding with localSearchFilter + debounce/queueSearchFetch to enforce a 3+ character minimum, avoid overlapping requests (pendingSearchFetch), and debounce fetches. Adjust fetchUsers to honor the search length and to compute/send an exclude_role parameter (and fix admin flag logic). Update store users action to include filters[exclude_role] in the query string.
Improve users filter UX and search handling
Update list.vue
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.
This pull request standardizes the naming of the "mitigate risk" stage across the codebase, changing it from
mitigate_riskstomitigate_riskfor consistency in both backend and frontend. It also updates the documentation for the WhatNow content API, clarifies the structure of the Prepare Messages API (V2), and improves Amharic language translations and labels.Stage naming standardization:
Changed all instances of the stage key from
mitigate_riskstomitigate_riskin backend models, frontend VueWhatNow/Prepare Messages API documentation improvements:
Expanded the docs to clearly distinguish between the V1 (legacy) and V2 (current) WhatNow content APIs, with detailed endpoint tables, query parameters, and explanations of the new V2 message object structure.
Updated API endpoint references in the documentation and example code to reflect the new V2
/preparemessagesresource and its usage.Frontend and backend code quality improvements:
Localization and translations: