-
Notifications
You must be signed in to change notification settings - Fork 889
chore: refactor Appearance to an interface callable by AGPL code #11769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @spikecurtis and the rest of your teammates on |
5c875b2
to
f168e58
Compare
d63b387
to
5ad6f3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! You probably already saw the tests but in case not I suppose in some tests we are not setting AppearanceFetcher
on the site handler or something like that.
f168e58
to
faa1f29
Compare
5ad6f3f
to
4fc8623
Compare
faa1f29
to
e980510
Compare
4fc8623
to
cdec5e1
Compare
e980510
to
eaabdb7
Compare
cdec5e1
to
79bee1c
Compare
eaabdb7
to
6a70ddf
Compare
79bee1c
to
529250f
Compare
6a70ddf
to
c980d65
Compare
529250f
to
25063cb
Compare
c980d65
to
38f23ea
Compare
25063cb
to
06d2b3d
Compare
06d2b3d
to
810bb6e
Compare
Merge activity
|
The new Agent API needs an interface for ServiceBanners, so this PR creates it and refactors the AGPL and Enterprise code to achieve it.
Before we depended on the fact that the HTTP endpoint was missing to serve an empty ServiceBanner on AGPL deployments, but that won't work with dRPC, so we need a real interface to call.