kv109/metafoodie-web

metafoodie-web's Issues

TripAdvisor może tylko link do strony restauracji jeśli się uda ściągnąć

Catch error regarding end of available API requests

Czy autocomplete moze pokazywac tylko restauracje?

check if printOutput works correctly

Remove Focus () on mobile

how to add second map below results

move mediaQuery function to beginning of js file

I can't do that :/

make provider errors catch looking nicer

remove NAZWA RESTAURACJI before loading results

set up github pages as testing server

Crashes if ipinfo.io request fails (e.g. when browser blocks such requests)

Standardize syntax to ES6

catch errors in fetches [missing places and so on]

Example in YELP FETCH

Make search results shareable

E.g. when I search for "Secret Life Cafe", I want to be able to share the link with the results, let's say https://metafoodie.netlify.app?query=Secret Life Cafe, Słowackiego, Warsaw, Poland

Isn't the map too small?

I get that you wanted to expose ratings. But I would like to be able to easily search through the map and click on restaurants. Right now the map is too short to do that.

On the other hand, one might simply want to check the ratings of the restaurant he or she already knows, sooo... 🤔 Not sure what's the best option. But for me using map has the higher priority. Ratings could be much smaller.

Providers link to details about restaurant

Mobile - maybe don't show a map by default - it is useless anyway

check searching bounds for mobile and desktop in regards to auto geolocation

zomato: dont show results if not appropriate

Change of warning when user choose not restaurant

You chose type, not.restaurant, now please.choose restaurant

add tooltips

preloader fallback of SVG arrow img [add alt=""]

Test browsers [e.g. incognito...]

change shareEndpoint for sharelink to domain-relevant variable

check if share link is created properly in new layout on production server

Don't expose client secrets

Possible solution: Move fetching functions (like foursquareFetch) to AWS Lambda where they can run as a node.js server.

Maybe add website of the restaurant

Fix ratings average algorithm

When there is a 0, the average is always 0.

Please verify if it's really an issue and provide an example.

do something with this ugle "Tu pojawią się wyniki..."

split JS code to modules!!!!

make preloaders look nicer

YELP appendData catch no reviews

YELP doesn't return score if no reviews in its database - print explanation of lack of score on table with scores

add preloader when loading results [there is one already, check it out]

Skeleton loading

remove CORS ANYWHERE from YELP FETCH URL

hovery duże zamiast linków przy nazwach providerów

Correct way of selecting Tags with name and rating in Scores Table

Now it is like:
const providerRatingTagEl = providerRowSelectorEl.firstElementChild.nextElementSibling;

Add ZOMATO fetch in frontend

Dont provide link in company's name if it has no website

Lokalizacja za zgodą przeglądarki / usera

don't load map javascript on mobile

Replace jQuery with vanilla JS

Replace jQuery with vanilla JS

load only required modules of bootstrap

change favicon

Move sharelink to separate function

Sharelink is unproperly created on localhost

localhost:5500/dist?query=Restauracja La Strada, 52, Alojzego Felińskiego, 01-563 Warszawa, Poland

On first click on the map, there is "/" missing, therefore link doesn't work

Could we start webpack-dev-server for testing purposes?

I'm tired of constant refreshing browser with WATCH...

Set map default location by GPS or IP

Catch error regarding end of available API posts

Add support for Tripadvisor

https://restaurantguru.com