-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect to API Gateway #153
Conversation
… kevmo/api-gateway # Conflicts: # components/ClaimCard.tsx
… available and proper env variables are set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevmo! Added some comments and questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kalvinwang I think this is ready for review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! Just some minor edits and questions about making tickets from todos. Also maybe add one more ticket for cleaning up types in index.tsx?
Co-authored-by: Kalvin Wang <kalvinwang@users.noreply.github.com>
|
||
import { Header } from '../components/Header' | ||
import { Main } from '../components/Main' | ||
import { Footer } from '../components/Footer' | ||
|
||
export default function Home(): ReactElement { | ||
export interface Claim { | ||
ClaimType: string | 'not working' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be ?? ''
for now and error handled later?
This PR represents our work connecting with the API gateway in a secure way. Some code/comments are there to mark places that need work once development from the API team is finished (e.g. the unique number header we are expecting from UIO, an API response with end user information in it rather than a placeholder).
Environmental variables (in a root-level
.env
file) are used to make the code more configurable in the event of URL/header/parameter changes in the future.===
Resolves #XXX