Background
==========
As part of our Squad-based ownership, we should stay on top of what
happens in these repositories. However, due to the number of
repositories (and subsequently pull requests) across the edX ecosystem,
it is challenging to stay on top of notifications, separating the
'signal' from the 'noise'. Email filters can go a long way to taming
Inbox notifications, but this is manual and requires maintenance as
Squad ownership changes. It also fails to account for Github-specific behavior.
Proposal
========
By leveraging Github support for `CODEOWNERS` files [1],
we can ensure that our team is at least CCed explicitly, here,
in the form a requested review. This request is just that, a request,
not a requirement; we are not enacting any new merge requirements
at this time.
- [1] https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
* docs: Specify component usage requirements in the README.
This includes both the component's dependency on @edx/frontend-platform, as well as its required environment variables.
* docs: fix verbatim formatting
* docs: improving footer README
Including headings and formatting consistent with frontend-component-header. Hopefully others soon.
* feat: upgrading deps, use logo from @edx/brand
* feat: upgrading peer deps
* feat: pr feedback
* update snapshots and example app
* pull config from AppContext
Co-authored-by: Adam Stankiewicz <agstanki@gmail.com>
* feat: use frontend-analytics directly
BREAKING CHANGE: handleAllTrackEvents is no longer part of the Footer props API. The footer uses frontend-analytics’s sendTrackEvent directly.
Also updating other dependencies to keep them up to date. This part should probably be a separate PR, technically.
* fix: remove unused dependency of frontend-logging
* fix: a little PR cleanup
* fix: putting frontend logging back
It’s needed by frontend-i18n and fails if it’s not there for tests.
* fix: pinning npm at 6
