-
Notifications
You must be signed in to change notification settings - Fork 19
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
Sprint 32 #520
Merged
Merged
Sprint 32 #520
Conversation
This file contains 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
Adding missing icons to fields on contact details, edit and new screens.
giving the fab actions a different color to help quickly identify each action.
on the group edit screen it used incorrectly a singular icon for group name instead of the group icon. And minor code cleanup.
Group name and Group type
Added around lines 3014 and 3100 the icon "Octicons" incon named "milestone".
fieldsIcons: { height: 20, width: 20, },
zdmc23
approved these changes
Dec 7, 2020
zdmc23
added a commit
that referenced
this pull request
Jan 27, 2021
* upgrade to Expo 39 * bump to v1.9 * make updates per new Notifications API: https://docs.expo.io/versions/latest/sdk/notifications/ * Hotfix to resolve issue where native-base "<Content>" component was causing a blank Settings Screen ActivityIndicator was not being displayed on some Android devices due to blending gray spinner into gray background; switch to Colors.tintColor resolves the issue * bump back to v1.9 after 1.8.1 hotfix * Sprint 29 (#482) * Resolves #423 * Resolves #350 * Resolves #425 * Sprint 29 (#487) * Resolves #458 * Sprint 29 (#488) * Resolves #420 * Sprint 30 (#489) * Resolves #468 * Sprint 30 (#490) * Resolves #484 * Sprint 30 (#492) * Resolves #169 * Sprint 30 (#493) * Resolves #357 * Resolves #474 * Sprint 30 (#494) * Resolves #474 * Sprint 31 (#498) * Resolves #491 * Resolves #497 * Sprint 31 (#499) * Resolves #497 * Sprint 31 (#511) * Resolves #495 * Resolves #512 - Test Automation IDs for Login workflow * Sprint 31 (#513) * Resolves #353 * update language schema to pass CI unit tests * Sprint 31 (#519) * Resolves #360 * Sprint 32 (#520) * Resolves #430 * Sprint 32 (#524) * Resolves #358 * Sprint 32 (#525) * Resolves #508 * Sprint 32 (#529) * Resolves #528 * Resolves #509 * Sprint 32 (#533) * Resolves #410 * Sprint 33 (#534) * Resolves #532 * Sprint 33 (#535) * Resolves #532 * Sprint 33 (#536) * Resolves #514 * Sprint 33 (#538) * Resolves #516 * Sprint 34 (#542) * Resolves #539 * Bump immer from 7.0.14 to 8.0.1 (#541) Bumps [immer](https://github.com/immerjs/immer) from 7.0.14 to 8.0.1. - [Release notes](https://github.com/immerjs/immer/releases) - [Commits](immerjs/immer@v7.0.14...v8.0.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Hans Smüller Rasch Diaz <raschdiaz@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
#430