FEAT: implement places APIs in ced-browser-fe#186
Closed
PierpaoloPirasSp wants to merge 14 commits into
Closed
Conversation
places APIs in ced-browser-fe
Collaborator
Author
|
PR #222 have all changes |
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
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.
Description
This Pull Request implements
/searchand/places/{placeId}endpoints from BEResolves IEG-2955
How to test
ced-browser-be(be sure to have correct env vars, make the complete DB migration and populate with some data)ced-browser-feSHA-256 hashed fiscal codeand paste it inTEST_USERSenv var/test-sesionAPI 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)/authorize?id={token}placesdetail API