-
Notifications
You must be signed in to change notification settings - Fork 0
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
Styling/form labels #101
Styling/form labels #101
Conversation
…o account for these changes
…ent to explain why the invocation is commented out
Thank you for getting this done so fast!! |
export const uploadPhoto = async (photo) => { | ||
try { | ||
const response = await fetch( | ||
"https://my-fly-box-api.herokuapp.com/api/v1/images", |
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.
A good call to move this to the ApiCalls. This make it the proper formatting for the fetch calls.
|
||
render() { | ||
return ( | ||
<View style={styles.container}> | ||
<Text style={styles.label}>Fly Name:</Text> |
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 for adding these labels for these input fields in the fly editing and adding page. This make things more understandable for the user when filling out fly information.
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.
You're welcome! Thanks for bringing this to the group's attention!
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 for adding the labels in the Fly form. This is a clean way to show the user what fields they are using.
Issue(s) related to this PR:
Type of change made:
If this submission is a new feature:
Change Log:
Were there any challenges that arose? If so, how were they addressed?
Technical Debt:
Testing:
Test coverage = 45.93%