egov app

Open
#2,314 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

The issue contains only an egov app JSON response and names no files, tests, or entry points. Clarify what documentation change is requested and define the expected result before locating the relevant documentation page or validation steps.

Written by the indexing model from the issue text.

Description

{
"status": 200,
"message": "OK",
"data": {
"id": 7470,
"pcn": "-",
"scope": "PROFILE_VIEW",
"tracking_no": "6476C80D54090",
"callback_url": "https://test.url",
"is_accepted": null,
"accepted_at": null,
"payload": {
"qr_value": "eyJpdiI6ImJQcG1INyt5RkF5QlpYXC91Zlh5NCtBPT0iLCJ2YWx1ZSI6ImtHcUYwek5DTkpXZWw1SklHSFd4TDlKQnRCQ3M3aW1iYmtkdHBrWTdMWFU9IiwibWFjIjoiZmQwNmRhMDM4ZjhjMWU0MWQxOWIzOGM1N2JmYmI5YWMwOTdiYWIxMjU1YjdmNWUwY2JmOWMwODRhYzE0ZGVmYyJ9"
},
"response": {
"uniqid": "MVPCBEUVCGPZR",
"email": "[email protected]",
"birth_date": "1998-01-24",
"first_name": "Josie",
"middle_name": null,
"last_name": "Dela Cruz",
"suffix": null,
"gender": "female",
"nationality": "Filipino",
"photo": "https://ucarecdn.com/7c0976e2-a60f-46eb-a97a-999e60e0a1eb/",
"mobile": "+639090000000",
"address": "#100 UGO TEST ADDRESS LINE 2, DOñA IMELDA QUEZON CITY, NATIONAL CAPITAL REGION (NCR), PHILIPPINES ",
"street": "#100 Ugo",
"barangay": "Doña Imelda",
"municipality": "QUEZON CITY",
"region": "NATIONAL CAPITAL REGION (NCR)",
"province": "NATIONAL CAPITAL REGION (NCR)",
"country": "Philippines",
"postal": null,
"address_line_2": "test address line 2",
"barangay_code": "137404031",
"province_code": "133900000",
"municipality_code": "137404000",
"region_code": "130000000",
"country_id": 175,
"foreign_address": null
}
}
}

Dominant language
Go
Stars
334
Forks
503
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ipfs/ipfs-docs

All issues in ipfs/ipfs-docs

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.