This repository has been archived by the owner on Aug 14, 2023. It is now read-only.
Issue #19 #242
Merged
Issue #19 #242
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
…tion name is empty
…e ignoring issue
…name data from geocoder function
|
This is tested and works fine. This is now ready for code review. |
|
Tagging the issue #19 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixed wrong results when enter location name.
Also now when you enter the name of a category or a tag in the place field it returns locations in that category or tag. It works only when you enter an exact name of a category or tag. It is possible to change this behavior to return locations when you enter a part of category name (LIKE comparison), but I think it's not good.