Website for the repo https://github.com/maartentibau/angular-logos that is dedicated to collecting all logos and badges that are inspired by the original Angular logo. The logos that can be found on this website can be related to conferences, Meetup groups, NPM packages or anything else that exists within the Angular universe.
When starting the app with a search param, it still displays the whole list.
Search works as usual, but not at initial startup...
Regression might have come in with the routing
All the logos displayed on the website are not owned by Angular Logos, we don't hold a license on it, so this should be clearly mentioned in the README of the repo and also a specific LICENSE file.
I just wanted to send a specific logo to someone or tweet about it and I was no able. The person needs to navigate the page to find it.
It would be nice to have a feature to have a URL to be sent and when it's open the receiver can see the logo that I want to share at a glance, maybe just an animation at the moment of load
So whenever a new logo is being added to the master branch of angular-logos repo it take a few minutes to become visible on the website. The reason for this is because with every merge we do a rebuild of the master branch to setup the GHPages of the angular-logos repo.
This is of course a little drawback to the user experience, maybe we should try to find out if it's possible to come up with a solution.
try to find out if a logo is really available yet on the GHPages site (if that means we need to do a check for every logo, this might maybe be a bit overkill, maybe we could store that info somewhere to only check for new logos?
we maybe could check the creation date of a file when we retrieve the data from repo, if the logo is at least 10min in the repo we show it. Important thing to note here is that we then need to keep track of it, because now we use a shareReplay on the request so that might something we need to look into then.
The data.service uses metadataUrl from the environment file.
For some reason, even though the production build is being run, still the request to the metadata.json file is the sample file.
Also when I try to serve the app locally in production mode, this seems to have no effect. No clue what is wrong.