Hey! I added the feature where it shows "No results found for the entered State, Pin code or Date, Please Try Again" in the NEW-UI branch. Let me know if there are any issues.!

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce?

This PR include Chart and ContinentChart component.

• What is the current behavior?

No errors, linting errors, and no test failures.

• What is the new behavior?

Now, Covid 19 Information shows Line Chart instead of Numbers.

• Does this PR introduce a breaking change?

No, breaking changes is there.

💯 Thank you!

:warning: This feature requires an Access Token provided by the Mapbox Library. Please make sure that you add this token to the .env. file as REACT_APP_MAPBOX_ACCESS_TOKEN ( see .env.example )

Creating the Access Token

• Create a MapBox account by navigating to this link
• After creating and verifying the account, go to https://accoung.mapbox.com and copy the access token
• Place the token in .env as REACT_APP_MAPBOX_ACCESS_TOKEN

Screenshots

Your checklist for this pull request

🚨Please review the guidelines for contributing to this repository.

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Please check if the PR fulfills these requirements

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • Feature

• What is the current behavior? (You can also link to an open issue here)

  • Results do not have a dedicated map component

• What is the new behavior (if this is a feature change)?

  • Each result-card has a map component ( which can be toggled by the user ) that renders the coordinates returned by the API.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Yes but only in one part of the UI

• Other Information:

  • @stephin007 The coordinates returned by the API is wrong and so the resulting render of the map won't match the actual address.
  • Future changes
    • A maker/tooltip component to display the address on the map with the tip pointing to the exact location.
  • Closes #20

❤️Thank you!

This branch adds a test feature to the Application.

Major Change:- downgraded React v17 to React v16 because adds extra functionality for React App.

Added Packages:-

• Jest
• Enzyme
• react-test-renderer
• enzyme-adapter-react-16
• enzyme-to-json

Closes #99

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• Bought State management(React context API ) to the app ..

• We can now access the req. data on any component!

❤️ Thank you!

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  • feat
• What is the current behavior? (You can also link to an open issue here)
  • no marker
• What is the new behavior (if this is a feature change)?
  • marker icon on each map
• Does this PR introduce a breaking change? (i.e changes that may require users to update/refactor existing istances of the application)
  • no
• Other Information:
  • closes #107

Screenshots

❤️ Thank you!

Feature: Adds basic scalable light/dark mode functionality using a wrapping Styled Component themeprovider + a MUI theme provider.

The useDarkTheme custom hook handles the styled component wrapper, which the MUI theme pairs with. All MUI features should work with dark mode now - if not let me know.

I included a Styled Component button for the toggle, but you could of course just make this a normal react feature and limit Styled Component integration to globalStyles only. globalStyles.js atm is using mostly simple selectors, but as things scale you can increase specificity ofc.

Let me know your thoughts on this second draft, thank you :)

Some ideas, obviously the button would ideally be a toggle within settings. I'm setting this to draft so you can look at the structure change ideas.

So far:

• Installed Styled Components
• useDarkMode hook to toggle between modes
• Theme controlled globally for scaling

Still needs:

• [ ] styles on Home.js need to be accessible by globalStyles, as Home.css are. This would require some refactoring afaik.
• [ ] MUI bg and text elements still static
• [ ] Button would ideally be in a nav or settings, and a toggle

Hopefully the idea is helpful even if it's to decide you don't want to do it this way at all!

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• docs update

• What is the new behavior (if this is a feature change)?

• added a new workflow

• Does this PR introduce a breaking change? (i.e changes that may require users to update/refactor existing istances of the application)

• NULL

• Other Information:

❤️ Thank you!

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master :yes
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream) : No conflict
• [x] Your Commit messages should make sense. : Yup
• [x] Don't push your package.lock.json as this project uses yarn.lock already. :ok
• [x] Check your code additions will fail neither code linting checks nor unit test. :ok

Describe your changes

• What kind of change does this PR introduce? : (Filter Bug Fixed)

• What is the current behavior? : (Not Have any Filter component)

• What is the new behavior (if this is a feature change)? : (Added a Filter Component for filtering vaccine)

• Does this PR introduce a breaking change? :(Nope)

• Other Information: (Nope)

❤️ Thank you!

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) New Feature

• What is the current behavior? (You can also link to an open issue here) No information related to COVID-19 around the world

• What is the new behavior (if this is a feature change)? New Page added

• Does this PR introduce a breaking change? (i.e changes that may require users to update/refactor existing istances of the application) No

• Other Information: This PR will be start to the issue 116

❤️ Thank you!

Is your feature request related to a problem? Please describe. Enable the website to be used as a native app by converting the site into an PWA(Progressive Web App)

All Ideas are welcome

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce? (Filter Component Structure Changed)

• What is the current behavior? (Multiple Filter Option Select at one time)

• What is the new behavior (if this is a feature change)?(User Can Only Select One Filter Type only)

• Does this PR introduce a breaking change? (i.e changes that may require users to update/refactor existing istances of the application)

• Other Information:

❤️ Thank you!

🚨 Please review the guidelines for contributing to this repository.

Please check if the PR fulfills these requirements

• [x] Make sure you are requesting to NEW-UI. Don't request other protected Branches like staging/master
• [x] Make sure no conflicts are present in the code, if so please resolve it(Tip: Always fetch upstream)
• [x] Your Commit messages should make sense.
• [x] Don't push your package.lock.json as this project uses yarn.lock already.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Describe your changes

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Bought Infinite scrolling

• What is the current behavior? (You can also link to an open issue here)

• resolves #158

• Other Information:

• NULL

❤️ Thank you!

Is your feature request related to a problem? Please describe. Right now project does not have paginated results when vaccine data is shown.

Describe the solution you'd like If we add pagination, this will be easy for the user to go to any page they like.

Any suggestion is welcome regarding this issue

Thanks🎉

Is your feature request related to a problem? Please describe. This feature will allow use to get browser notifications when a slot is available

Describe the solution you'd like Right now, not sure how to achieve this, but found some docs in Mozilla docs : https://developer.mozilla.org/en-US/docs/Web/API/Notification

Would love to assign who have a clear and concise solution for this.

Thanks ❤️

Note: These changes have been made only to the files mentioned ( indirectly ) in the issue. I haven't looked at the other files :sweat_smile:.

Major Changes

• Completely refactored the Home Page and VaccineDataSingle component to be more responsive and scalable
• Extracted some of the redundant components to their own lexical environment ( Will be creating issues for code blocks that can be refactored the same way )
• Created a single-source-of-truth for CSS ( for the Home page and the component ( mentioned above ) ) at /src/lib/useClasses.js

Minor Changes

• Replaced some of the conditions with regular expressions ( Still a lot of places where this change can be made )