Skip to content

FEAT: implement places APIs in ced-browser-fe#186

Closed
PierpaoloPirasSp wants to merge 14 commits into
mainfrom
IEG-2955
Closed

FEAT: implement places APIs in ced-browser-fe#186
PierpaoloPirasSp wants to merge 14 commits into
mainfrom
IEG-2955

Conversation

@PierpaoloPirasSp

@PierpaoloPirasSp PierpaoloPirasSp commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

Note: This PR depends on #191 . Please review and merge #191 first.

Description

This Pull Request implements /search and /places/{placeId} endpoints from BE

Resolves IEG-2955

How to test

  • Configure and run ced-browser-be (be sure to have correct env vars, make the complete DB migration and populate with some data)
  • run ced-browser-fe
  • make authorize login with this steps:
    • generate a correct SHA-256 hashed fiscal code and paste it in TEST_USERS env var
    • call /test-sesion API passing the correspective fiscal code in a body like this: { givenName: string, familyName: string, fiscalCode: {your_fiscal_code} with auto-redirect disable (so you could easily pick the correct token from location Header)
    • use that token in FE application calling /authorize?id={token}
    • if all is set correctly, you will have authentication token through all APIs
  • search an element, verify query works correctly
  • click an element, verify that navigation is correct (for now it will redirect to `/enti/{entityID}/punti-di-accesso/{id})
  • verify data is read from places detail API

@PierpaoloPirasSp PierpaoloPirasSp changed the title Ieg 2955 FEAT: implement places APIs in ced-browser-fe Jun 17, 2026
@PierpaoloPirasSp

Copy link
Copy Markdown
Collaborator Author

PR #222 have all changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants