iamhaseebn opened a new pull request, #308:
URL: https://github.com/apache/fineract-backoffice-ui/pull/308

   ## What and why
   
   Report execution hardcoded Office and two dates even though Fineract defines 
each report parameter dynamically. This change discovers the selected report 
template, renders every supported control type, fails closed for unknown types, 
and sends the complete named R_* parameter map for both HTML and CSV execution.
   
   Closes #300
   
   ## Verification
   
   - `npm run lint`
   - `npm run format:check`
   - `npm run i18n:check`
   - `npm run check:icons`
   - `npm run build`
   - `TZ=UTC npm test -- --watch=false --browsers=ChromeHeadless` - 851 tests 
passed
   - `npx playwright test e2e/report-enhancements.spec.ts e2e/reporting.spec.ts 
e2e/functional-coverage.spec.ts --project=mocked --workers=2` - 45 tests passed
   - `npx playwright test e2e/report-parameter-backend.spec.ts 
--project=backend --workers=1` - backend setup and regression test passed 
against a real local Fineract stack
   - The mocked flow verifies both `R_officeId` and `R_loanOfficerId` in the 
outgoing query
   - The backend flow seeds clients in two offices and proves that changing 
Office changes the returned Client Listing row set
   
   ## Screenshots
   
   A screenshot and short recording of the dynamic report parameters are 
attached in the evidence comment below.
   
   ## Checklist
   
   - [x] I did not hand-edit generated files under `src/app/api/`.
   - [x] New component or service code avoids direct browser globals and 
imperative third-party APIs.
   - [x] User-facing strings use translation keys.
   - [x] I added unit, mocked e2e, and real-backend regression coverage.
   - [x] UI workflow changes include suitable e2e coverage with both mocks and 
a real Fineract backend.
   - [x] The commit is signed and includes the Signed-off-by trailer.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to