-
Notifications
You must be signed in to change notification settings - Fork 91
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
BZ#1471301 - Login/nav brand and logo are set by api #1513
BZ#1471301 - Login/nav brand and logo are set by api #1513
Conversation
a2732be
to
bcda20f
Compare
@miq-bot add_reviewer @epwinchell |
Soo.. the problem with this is that "skins" work by replacing a few things, including:
It looks like the API is serving the right images in that case, so the images should be fine. We should also update But.. I'm still seeing
so maybe that one should also be using |
bcda20f
to
aeb04e5
Compare
Great points @himdel !! Updated pr as per feedback... what do we think about the @skateman i think the only thing thats kinda ah bummer, we're not setting brands and logos specific to the sui... so whatever is set for cui is same here... so yeah, we're missing |
@himdel can we actually have skins since we're not exposing JS precompilation? |
a413a8e
to
674b420
Compare
Checked commit AllenBW@674b420 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Thanks! :) Still seeing
that are not used now. As for text, I kinda like the idea of SUI not caring about skins at all (except for pure CSS) and just getting all that from the API, so maybe we can just tack on +Self Service? (Although, not sure about the i18n aspect of that..) |
@skateman Yes we can, they (whoever) just have to build it themselves :) |
Leavin' in the images wasn't an oversight, it was intentional, to reduce pr commotion and then who knows, maybe someone will want em? But if yah really really want me to remove em, will do @himdel |
Aah, thanks :) Just one last think, I think... it's never using the images now...
I'm guessing we need... diff --git a/client/app/core/appliance-info.service.js b/client/app/core/appliance-info.service.js
index b195e911..98f741d1 100644
--- a/client/app/core/appliance-info.service.js
+++ b/client/app/core/appliance-info.service.js
@@ -27,8 +27,8 @@ export function ApplianceInfo ($sessionStorage) {
server: data.server_info.appliance,
asyncNotify: data.settings.asynchronous_notifications || true,
nameFull: data.product_info.name_full,
- brand: data.product_info.brand,
- logo: data.product_info.logo
+ brand: data.product_info.branding_info.brand,
+ logo: data.product_info.branding_info.logo
}
$sessionStorage.applianceInfo = applianceInfo |
edb339a
to
a2c4f92
Compare
In dev, these things will appear as broken images, but upon build, they show up just fine
a2c4f92
to
5e9bc85
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.
Verified I'm now seeing requests for those images in the console 👍
Looks like supporting showing the images in devel mode is non-trivial, we could make webpack-dev-server proxy (Or maybe we can move all the images to CUI and just do that, but not sure that's the right direction, unless there's a plan to merge the 2.) |
sad emoji, yeah gonna kinda given up on em workin in dev, maybe it'l be worth it to make a note in dev docs, for posterity n stuff |
@AllenBW Can this be |
@simaishi should be a clean merge as there hasn't been too much churn on the files this touches.. 🤔 |
…rand BZ#1471301 - Login/nav brand and logo are set by api (cherry picked from commit c385bad) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1693757
Hammer backport details:
|
fixes https://bugzilla.redhat.com/show_bug.cgi?id=1471301
In dev, these things will appear as broken images, but upon build, they show up just fine
Styling on login is a little jacked up atm... but we're applying the same classes so 🤷♂️
What we look like (note the url
ui/service
)