GithubHelp home page GithubHelp logo

warsinhk's Introduction

COVID-19 in HK|武漢肺炎民間資訊

This is the repository for covid19.vote4.hk

📍 Data

The data is updated automatically every 5 minutes. The information are all open for use. If you wish to cite anything from this site, please credit us as covid19.vote4.hk - COVID-19 in HK or covid19.vote4.hk - 武漢肺炎民間資訊.

🚀 Quick start

Set up your environment

Navigate to the project directory and run the below command to install all the dependencies of project

yarn

Start your local development

gatsby develop

Your site is now running at http://localhost:8000!

Note:

  • You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.
  • Gatsby requires Node.js 10.13.0 or higher. If your version is below the required one, try to upgrade it or following the below steps to switch to the desired version using nvm: Run the following command to use the version from inside the .nvmrc file
    nvm use
    If the specified version is not found, please run the following command to install
    nvm install

🌟 How to contribute

All contributions are welcome.

For Volunteers:

  • Apply through Google Form.
  • Submit Github Issues for reporting bugs. (See below Issues section for more).

For Developers:

  • See below Development section for more.

Issues

  • Please follow our issue template when creating an issue. We only accept bug report and feature request. Before creating an issue, make sure there is no similar issues.
  • If you plan to work on an issue, please leave a comment to inform us and we will assign it to you. We recommend beginners to pick up issues with good first issue tag.

Pull Requests

  • Please follow our pull request template when creating a pull request. Make sure your pull request fulfils our requirement.
  • Please create a new branch (for each PR) based on the latest dev or the feature branch and name it either feat/<meaningful_name> or fix/<meaningful_name>.
  • Please follow our naming convention 🌟[feat/fix]: [summary] (pick your favourite emoji 😉) for pull request title.

Communication

  • We make communication in a Telegram Group. Feel free to join us by clicking here.

💻 Development

Branches

Purpose Branch URL Remarks
Development dev https://wars-dev.vote4.hk/ Default development branch. All pull requests will be reviewed and then merged to this branch
Production master https://covid19.vote4.hk/ Only pull requests created by administrators are allowed
Hotfix fix/* None Fixes created by the administrators
Feature feat/* None Features branch before merging to Development branch

Checkout the latest code

Please setup dev repo github.com/nandiheath/warsinhk as upstream and git fetch upstream -p everytime before making commits. And remember to rebase your branches onto latest upstream:dev.

Internationalization (i18n)

We are using react-i18next to assert that the internationalized content can be loaded or that it gets rendered when the language changes.

The translation json files for en and zh are located at src/locales/en/translation.json and src/locales/zh/translation.json respectively. By default, zh is used. If you have changes to the wordings, please make sure they are added or updated in both json files.

Examples:

src/locales/en/translation.json

{
  "world.page_title": "Global Cases"
}

src/locales/zh/translation.json

{
  "world.page_title": "全球疫情追蹤"
}

Use useTranslation() for functional components:

// 1. import useTranslation from react-i18next
import { useTranslation } from "react-i18next"
// 2. define t from useTranslation()
const { t } = useTranslation()
// 3. use the t function with the key as the parameter
const title = t("world.page_title")

Use withLanguage() to translate the target field within an object

// 1. import withLanguage from custom utils
import { withLanguage } from "@/utils/i18n"
// 2. define i18n from useTranslation()
const { i18n } = useTranslation()
// 3. pass i18n, the target object, and the target field name to withLanguage
// if the locale is en, the link would be ``node.address_en``
// if the locale is zh, the link would be ``node.address_zh``
const address = withLanguage(i18n, node, "address")

Use getLocalizedPath(i18n, path) to get the localized path

// 1. import getLocalizedPath from custom utils
import { getLocalizedPath } from "@/utils/i18n"
// 2. define i18n from useTranslation()
const { i18n } = useTranslation()
// 3. pass i18n and the path to getLocalizedPath
// if the locale is en, the link would be ``/en/world``
// if the locale is zh, the link would be ``/zh/world``
<Link
  href={getLocalizedPath(i18n, "/world")}
>
  ...
</Link>

For interpolation, surround the dynamic value by curly brackets in translation.json

{
  "world.border_shutdown_last_update": "Last update: {{date}}"
}

and pass an object with the key defined in curly brackets and the dynamic value in the second parameter

{
  t("world.border_shutdown_last_update", { date: last_update })
}

Analyse code for potential errors

Run eslint to ensure it fits linting

yarn lint
yarn lint:fix

Try to build to see if there are any errors.

yarn build

📄 License

This software is released under the MIT License, while the content on this site is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

warsinhk's People

Contributors

csvke avatar cswbrian avatar dependabot[bot] avatar dhoeric avatar elvinyhlee avatar fionnachan avatar gabrielkoo avatar gotoanddie avatar himphen avatar hosiukeung avatar howawong avatar jasonhk avatar johnhorsema avatar kalvin807 avatar khmak3 avatar lifehome avatar nandiheath avatar nandikinto avatar openhealthhk avatar poyea avatar rholais avatar rogerso avatar tonyhhyip avatar virenmohindra avatar wingkwong avatar yookoala avatar yshing avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

warsinhk's Issues

Frontpage statistic and cases page mismatch

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    A bug.

  • What is the current behavior?
    The frontpage stated that there is only 5 new cases on the frontpage summary (as rendered on 23rd March, 2020) while I counted 39 cases confirmed on 23rd March in the Cases page.

The frontpage summary (captured at 14:53, 24th March, 2020):
2020-03-24 14-53-53 的螢幕擷圖

The cases page (captured at 14:57, 24th March, 2020) shows at least the first 6 cases to be confirmed on 23rd. The page is long, but I counted 39 total cases:
2020-03-24 14-57-17 的螢幕擷圖

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
    As demonstrated above.

  • What is the expected behavior?
    The figures should be consistent with the cases list, or there are other display issue that caused the misunderstanding.

  • What is the motivation / use case for changing the behavior?
    To better communicate the epidemic situation.

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]

Improve English Translations

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
  • What is the current behavior?
    The English translation has many cases of awkward phrasing and odd usage in general.
    In the High-Risk Areas page, the text in the legend is so long, it causes the legend to cover most of the map on mobile. This makes the map difficult to use in mobile.

  • What is the expected behavior?
    Better translations

  • Please tell us about your environment:
    Doesn't matter, it's a translation fix, so strings only.

  • Other information
    I shall submit a pull request myself to fix this as soon as possible.

[Case Individual Page] First show English lang and jump to Chinese lang, SEO in English

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    https://wars.vote4.hk/cases/1
    Even I visit a Chinese individual page, the page first show English language and then jump to Chinese language, while SEO is in English

image

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

looking for a updated CSV for 2022

hello @lifehome , happy lunar new year,

Our research (with @wmml1234567890 ) on COVID-19 is still running, but we are lacking the CSV file for 2022, could you please offer a help?

Thank you for your kindly attention

Originally posted by @JakeSLLeung in #244 (comment)

hello,

As mentioned, we hope to get the link of csv file for 2022, would you please offer a help to our research? Thank you very much.

Slow performance of case pages

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    Report a bug,

  • What is the current behavior?
    All are reproduced in Chrome in Google Pixel 3a.
    The page is slow when the user toggles between avatar or card views.
    In avatar view, the page is lag if user opens/closes a few cards

Suggestions:

  • add spinner to indicate the page is loading.
  • Use infinite scroll or lazyload technique.
  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: Mobile Chrome
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Add share button for individual case

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    In each case card, add a share button to share individual case. The link should be wars.vote4.hk/cases/<case_no>

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Clicking link in high risk page causes runtime error

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    Bug

  • What is the current behavior?
    the app crashes on high-risk map page

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

go to https://wars.vote4.hk/en/high-risk/
click on case #275
page is blank and shows error below

Uncaught (in promise) Error: Invalid LatLng object: (NaN, 114.131)
    at new N (leaflet-src.js:1333)
    at U (leaflet-src.js:1406)
    at e.initialize (leaflet-src.js:7071)
    at new e (leaflet-src.js:349)
    at Object.t.marker (leaflet-src.js:7336)
    at i.dataPointToMarker (highRiskMap.js:240)
    at Array.map (<anonymous>)
    at n.<anonymous> (highRiskMap.js:261)
    at u (runtime.js:69)
    at Generator._invoke (runtime.js:288)
  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [Chrome latest]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Updated csv for Confirmed cases

Hi, we are currently having on a research for COVID-19. But we couldn't find the latest csv for "Confirmed cases", please help.

Thank you very much.

cannot run with older node version (<=10)

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    Failed to build on node10

  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Probably this is because we are using string.matchAll which is a node12 function. We better find an alternative for this.

Case page accept query strings for preset view/search filter keys/group

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...
    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

Case page should accept query strings which accept preset view/ search filter keys/ groups
image

Example applications:
When user clicks 「確診」in index page, it can land on cases page with 「確診」filtered in the search bar
When user clicks the map in index page, it can land on cases page with the sub-districts filtered in the search bar

  • Do you want to request a feature or report a bug?

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

[World] Add case per 1 million people

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • [ x] feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    Add case per 1M people in https://wars.vote4.hk/world, just like https://www.google.com/covid19-map/

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Add group description under the group name

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
      If group description is available, the group description text should place under the group name
      image
  • Do you want to request a feature or report a bug?

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Reduce size of case data

  • I'm submitting a ...

    • bug report
    • feature request
  • What is the current behavior?
    Currently, there is a lot of redundant data in the table of cases - items like names of hospitals, patient status, case type, residency, citizenship and classification are typed out in both English and Chinese, which is a waste of space, and should be replaced with a common ID.

Also, the source URLs can become fairly long; it would be a good idea to pass every URL through a URL shortener.

This may be a tiny problem at the moment, but it will save significant amounts of bandwidth when the number of cases increase significantly - which is very likely for COVID-19.

  • What is the expected behavior?
    The database - which we serve to every single device that views the cases page - should be more compact.

  • Other information
    At the moment, status and classification are the only two columns with a common ID already in the table; I will submit a pull request that modifies CaseCard.js to use the language-agnostic columns, and removes the columns from the query in cases.js. This tiny change saves about 60KB with 411 cases.

Also, the classification for case 377 is incorrectly capitalized.

Global Cases Improvement suggestion

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?

  1. As a user, I want to go to the corresponding source/ consulate page for further information.

  2. As a user, I also want the information from the airline companies of the special pandemic arrangement, so that I can find travel-related information easily.

What is the expected behaviour?

  1. Each chip has a clickable link to the corresponding page.
  2. New tab displaying information about airline arrangement

What is the motivation/use case for changing the behaviour?
Small change to chip component with no library change.
A new tab in Global Case tab list

I can work on it if you guys think these are good to have feature. :)

Search / Filter asymptomatic cases

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    When user type 'asymptomatic' 「無病徵」in the search bar, it will filter the corresponding cases
    image

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Request for CHP number of local case group

Hi, we are doing a research on local COVID-19 database.

We see the case can be classified by group (e.g. Dancing/Singing Cluster)
But we couldn't find the csv for CHP number of those group, could you please kindly help?

Thank you in advance!

feat: Global Cases tab

Me and my friend (Designer) are willing to contribute in this project.

I'm submitting a ...

  • feature request

Reason

  1. Coronavirus is spreading out quickly across world (South Korea, Iran, etc.). It will be helpful if we include summary of global situation.
  2. There are similar dashboards out there but most are in English and Simplified chinese, I would like to make a Traditional chinese version.

Detailed explanation

Sketch
This is definitely a draft, without any style and concrete content.
If you guys are ok with the idea, my designer friend is going to help in redesigning the page.

image

Add asymptomatic figures at the summary

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    Add asymptomatic figures at the summary (hex code: #4f5096)
    image

  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Please tell us about your environment:

    • Version: 2.0.0-beta.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Map zooms out when the same location is clicked

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • [ x ] bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?

A bug.

  • What is the current behavior?

In the high risk map, when a location is clicked, a popup will open. When user click on the map, the popup will be closed. When the same location is clicked again, the map zooms out instead of focusing on the location.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Scenario 1

  1. Click on a location in high risk map
  2. Click on the same location, the map zooms out

Scenario 2

  1. Click on a location in high risk map
  2. Click on an empty space on the map, the popup closes
  3. Click on the same location, the map zooms out
  • What is the expected behavior?

Scenario 1
The popup should close but the map should not zoom out

Scenario 2
The location should be focused

  • What is the motivation / use case for changing the behavior?

The map is jumping to unexpected area. User needs to zoom in to the area the he was viewing. That is quite inconvenient.

  • Please tell us about your environment:

    • Version: 0.1.0
    • Browser: Chrome Version 80.0.3987.149
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

The issue is caused by the state activeDataPoint not being cleared when the popup is closed. Suggest to fix it either by listening on the popupclose event to clear activeDataPoint. Or by checking if the popup is currently open in the getActiveHandler method.

Use id attribute for scrolling in case page

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    Add attribute in WarsCaseCard component

  • What is the current behavior?
    Use a function to scroll when loading element the first time

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?
    It doesn't need a library and it works on most of the browser (except IE on XP)

Map zooms out unnecessarily when focusing on a location

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • I'm submitting a ...

    • [ x ] bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • Do you want to request a feature or report a bug?
    A bug. (I would say an enhancement but that seems not to be an option here)

  • What is the current behavior?

When a location is clicked, the map zooms to level 15 disregarding current zoom level.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
  1. Click on a location
  2. Zoom in closer
  3. Click on another location
  • What is the expected behavior?

The map should focus on the new location without zooming out.

  • What is the motivation / use case for changing the behavior?

When user zooms in a location, the user is interested in the surrounding area. When he clicks on a nearby location, the map shouldn't zoom out.

Since the high risk locations is dense already, zooming out will present the users with even denser locations. User often has to zoom back in.

  • Please tell us about your environment:

    • Version: 0.1.0
    • Browser: Chrome Version 80.0.3987.149 (Official Build) (64-bit)
    • Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Currently the max zoom level is set at 15 when clicking on a location. Suggest to use option like:

{
  maxZoom: Math.max(15, this.map.getZoom())
}

Can't fetch `sub_district_en` from WarsCaseLocation table

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    I get this error while running gatsby develop
    image
    Reason: The field is missing in spreadsheet
    image

Add loading indicator to cases list

  • I'm submitting a ...

    • bug report
    • feature request
  • What is the current behavior?
    The cases list just freezes until new cases are loaded in.

  • What is the expected behavior?
    Something should indicate that the page is actually loading...

  • Other information
    I'll submit a pull request to fix this.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.