* #3469 Update Gradle Play Publisher to resolve issues with travis build - update GPP/Gradle and use jacoco-android fork with gradle 6.0 support
* #3469 Update Gradle Play Publisher to resolve issues with travis build - remove extraneous space
* Added Support for System Wide Dark Theme
* changed methods to private
* Moved Strings to strings.xml
* Used Dagger to reduce code repetition
* Changes made as per review suggestions
* Minor Changes
* Fixes as per suggestions
* Minor Fixes as per suggestion
* made the variables static
* removed irrelevant code
It's common for users to expect that re-opening the app would
allow them to "continue where they left off". This also applies
for the case where they leave the app after opening an
external link. It's natural for them to expect that they would
see the webpage they left open when they re-open the app. This
doesn't happen for our app as we open custom tabs in a separate
activity. As a consequence, this makes the experience
un-intuitive.
Fix this by opening custom tabs in the same activity.
Fixes: #2944
Co-authored-by: Adam Jones <jones_adam@rocketmail.com>
* ic_custom_greyed_out_marker: removing grey marker
* NearbyParentFragment: changing function name and description
* change method name to hideAllMarkers
* Avoid showing the quiz pop-up twice to the user
Due to the current flow of code it's possible that in
some cases the quiz pop-up is shown to the user twice.
This is unnecessary and unintentional.
So, change the logic in such a way that the quiz pop-up
would be never be shown twice to the user.
Fixes: #3281
* Quiz: remove unused parameters from methods
Some methods don't seem to be using the parameters that
they receive. So, just remove the unused parameters.
It makes sense to not show the review activity for logged
out users for the same reasons that we don't allow users
to upload images.
We're even considering to limit the review activity to users
with a particular level of achievement[1]. So, it's valid to
not show review activity for logged out users who don't
have achievements levels at all.
[1]: https://github.com/commons-app/apps-android-commons/issues/2852
* Fixes#3303
* Refactor Nearby to alig lifecycle methods
* Pass updated place list to listfragment
* Added default zoom rate to mapbox
* Removed NearbyListFragmet and added the ui login to handle the same in NearbyParentFragment
* More code refactor
* Make BottomSheetList hideable
* onFragmentHide, hide the bottom sheets
* BigFix, Fragmet visibility, register/un-register camera move based on fragments lifecycke
* More code refactor
* Let the ExecutorUtil have non-ui thread
* Add Location Marker on non-ui thread (the non-ui stuffs)
* BugFixes
* Removed configchanges "orientation" from MainActivity in Manifest (That was messing with the fragment lifecycle)
* Some null checks
* Initialise lastknown location in onMapReady
* UI Fixes
* Adjusted UI to support dark and no-dark themes both (in nearby)
* Do not update map on Location Slightly changed
* Fix failing test case, let TestCommonsApplication extend Application instead of CommonsApplication
* start map view when nearby is visible
* start the map when NearbyFragmet is visible
* More bugfixes
* Added DUMMY view for NearbyPresenter's onDetach State
* Added a wrapper frame layout parent for MapView to preven it from drawing above other views
* More bugfixes (Fixes#3287)
* Gray out the un-selected markers from the nearby filter list
* BugFix, search this area should search the nearby places for the current camera position
* More BugFixes
* Handle null primitives with proxy
* Current location marker flow via permission flow
* onCameraMove should have null-check on NearbyController.latestSearchLocation instead of currentLocation
* Search for places around last focus location
* Handle location updates
* If the user is browsing the map, donot update the map with current location
* CategoriesModelTest: add methodA test for categories search
* CategoriesModelTest: use lateinit wherever possible
* CategoriesModelTest: make method name meaningful
* CategoryClient: fix category search case-sensitivity by converting to lower case as MW api is inherently case-sensitive, the results obtained will be same
* CategoryItem: reverting javadoc changes
* CategoriesModel: make category search case-insensitive
* CategoryItem: fix whitespaces
* Add tests for case-insensitivity
* CategoryClientTest: add more test cases
* CategoryClientTest: fix travis ci test
* CategoriesModelTest: changes mage to CategoriesModel and tested
* TextUtils: add mock textUtils for tests
* TextUtils: add more methods to mock for testing
* UploadControllerTest: fix the test resulting travis ci to fail
