https://github.com/nazmulidris/places-api-poc
This project shows how to exercise the Google Places API surface, Material Design 2 Components, JUnit5, mockK, Dagger2, and Kotlin
https://github.com/nazmulidris/places-api-poc
android dagger2-android junit5 kotlin-android material-design-2 material-design-components mockk places-api
Last synced: about 1 month ago
JSON representation
This project shows how to exercise the Google Places API surface, Material Design 2 Components, JUnit5, mockK, Dagger2, and Kotlin
- Host: GitHub
- URL: https://github.com/nazmulidris/places-api-poc
- Owner: nazmulidris
- License: apache-2.0
- Created: 2018-08-28T21:19:37.000Z (over 6 years ago)
- Default Branch: main
- Last Pushed: 2021-04-23T01:11:35.000Z (about 4 years ago)
- Last Synced: 2025-03-24T22:51:12.486Z (about 2 months ago)
- Topics: android, dagger2-android, junit5, kotlin-android, material-design-2, material-design-components, mockk, places-api
- Language: Kotlin
- Homepage: https://developerlife.com/
- Size: 10.8 MB
- Stars: 8
- Watchers: 3
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# Android app that tests Google Places API for Android
This project shows how to exercise the Google Places API surface.
# App in action
# Documentation
To learn more about this app, please check out these articles on developerlife.com
- [Depedency Injection](https://developerlife.com/category/DepedencyInjection/)
- [Test driven development in Kotlin & Android](https://developerlife.com/category/TestDrivenDevelopment/)
- [State management](https://developerlife.com/category/State/)
# Change master to main
The
[Internet Engineering Task Force (IETF) points out](https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1)
that "Master-slave is an oppressive metaphor that will and should never become fully detached from
history" as well as "In addition to being inappropriate and arcane, the
[master-slave metaphor](https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/HOWTO.ask?WT.mc_id=-blog-scottha#L231-L232)
is both technically and historically inaccurate." There's lots of more accurate options depending on
context and it costs me nothing to change my vocabulary, especially if it is one less little speed
bump to getting a new person excited about tech.
You might say, "I'm all for not using master in master-slave technical relationships, but this is
clearly an instance of master-copy, not master-slave"
[but that may not be the case](https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html).
Turns out the original usage of master in Git very likely came from another version control system
(BitKeeper) that explicitly had a notion of slave branches.
- https://dev.to/lukeocodes/change-git-s-default-branch-from-master-19le
- https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
[#blacklivesmatter](https://blacklivesmatter.com/)