tibudiyanto / jakarta-vax-availability Goto Github PK

Under detail_lokasi there is a lat lon. Would be nice if we can sort by lat lon sort by current location to the vax location

Long story short, this shouldn't happen:

Description

With the recent changes to the API, it seems that the "waktu" property on "jadwal" has gone missing, therefore the time is missing from each schedule.

Expected Behaviour

The time should display properly on the schedule.

Additional Information

It looks like the API schema has changed:

Tasks

• Add "floating" shadow effect to map page flyout
• Redesign "Back" button
• #31

Description

Huge bundle size, and very high TBT

Expected Behaviour

800kB is definitely excessive. We should aim at most 200kB based on recommendation alone. Less would be better

Additional Information

Description

The index page should be refactored into several smaller modules to reduce the number of lines of code.

Implementation Model

Tasks

• #44
• Move components that contain logic to modules/ folder, separated each by feature folders
• Move essential helpers into helpers/ folder

Description

At the moment, the Kuota service fails intermittently, and by default we currently fall back to showing each of those facilities as having 0 kuota, which is obviously incorrect. We should handle this fallback state correctly.

Expected Behaviour

A fallback state should be displayed when Kuota service fails.

Additional Information

Tweet thread: https://twitter.com/BukanYahya/status/1412283847341854720

Description

The VaxLocation card's header is currently overflowing and pushing the distance and quota badge out of view.

Expected Behaviour

The VaxLocation card's header should properly truncate.

Additional Information

Let's go back to the Tailwind Play URL from the mockup and take a look at which styles we're missing.

At the moment, it is not responsive enough on mobile device.

Help is very appreciated!

put it somewhere cute will you ;)

Description

With the recent update to the vax API, the site's now loading slowly due to the number of data. We should implement some form of pagination to help reduce the number of content rendered.

Implementation Model

A basic pagination query of the API is now available on the API. https://jkt-vax-quota.vercel.app/

Available queries: start (default 1) and count (default 100).

e.g. https://jkt-vax-quota.vercel.app/api/kuota?start=10&count=100

Tasks

[TODO]

We should tweak our current app icon so that it's ready for PWA implementation. For sizes, etc. see #41.

cc: @nibraswastaken

Description

Follow up from #40

Clicking on location icon in map doesn't focus back if the map moved to different lat/long

Expected Behaviour

It should focus back to current location with fit bounds

Additional Information

Description

There are some cases where the facilities are marked as being outside of Jakarta, which makes the map look like this.

Expected Behaviour

• Facilities' location should be labelled correctly.
• Facilities outside of Jakarta shouldn't be visible.

Additional Information

This might be happening on the API side. Some of the detail_lokasi data returned from the API can be inaccurate, as seen from this example:

Tasks

• #2
• #36
• #38
• #10
• #66
• Apply redesigned VaxLocation card

Because a good codebase is like a clean table. (Not my quote, I stole it from a friend.)

Current tasks

• #18
• #16
• #32
• #28
• #29
• Add VSCode config
• #47
• #57
• #59

Reference: https://twitter.com/resir014/status/1411971069515210752

Current tasks:

• #23
• #24
• #25
• #43
• Redesign - UI components

Description

I think adding analytics like

• track page views
• how many visitor and demographic

Implementation Model

Provider:

• Google Analytics
• Matomo
• Simple Analytics

map-equivalent "sort" of #2 , maybe we can set current location as the center of the map with zoom level adjusted so at least X number of vaccination location is visible on the screen

feel free to ignore

Tasks

• #34
• #47

Description

Some data have incorrect location, for example RSUD TANAH ABANG has the detail_lokasi of another hospital in Kallimantan.

Expected Behaviour

They should have the correct location, or maybe just redirect to Google Maps with the location name as search keyword?

Additional Information

Perhaps this should not be reported here, as it's more a bug in the API (data) side, but I'll leave it here for now. Feel free to close this.

Description

Some facilities do no provide totalKuota and sisaKuota data on their schedules, which causes our recent build failures.

For reference, this applies to this popover. We should add a case so that we can show an "invalid" screen when the Kuota data from each schedule time is missing.

Expected Behaviour

The schedule popover should correctly handle the case when no Kuota data is available.

Additional Information

Tweet(s) from @k1m0ch1:

are you using the key jadwal.waktu.kuota.sisaKuota ? it still alive, but I see a new key in here the "kuota" key from jaki

https://twitter.com/BukanYahya/status/1415538234881318912

I assume some location does not have a "waktu" key or "kuota" key thats why the sisaKuota is error, I think you need to add the handler to check the existence of "waktu" and/or "kuota" key

https://twitter.com/BukanYahya/status/1415540609922723842