Skip to content
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

[ Question ] Detecting which theme is being used, 'Classic' or 'Modern' in Page Interaction #1307

Open
yendrrek opened this issue May 17, 2022 · 3 comments
Labels
requires discussion This issues needs to be reviewed before development can start

Comments

@yendrrek
Copy link

Is there a way to access the object which contains 'themeName'?
I would need it in my Page Interaction to detect whether the user is using the classic or the modern theme.

image

@yendrrek
Copy link
Author

yendrrek commented May 17, 2022

When you console.log the API object you can see in globals:settings: defaultNovoThemeName: "modern-light" for both themes, the Classic and the Modern. It would be good to have defaultNovoThemeName: "classic" if the Classic theme were on.

@bvkimball
Copy link
Contributor

Hi @yendrrek , since PageInteractions are a feature of the Bullhorn ATS and no code is used from the component library, there is not much we can do here. I will escalate this to our product teams as a feature request. Can you give us a few more details in your use case here, are you injecting styles?

I will keep this ticket open temporarily, to notify you if this feature is getting added.

@yendrrek
Copy link
Author

Hi @bvkimball, yes, I'm injecting a style with a different colour into the banner / header on the Candidate record depending on the value in the 'Status' field. I made it work for the 'Modern' theme, but when using the 'Classic' theme it would not work properly. I eventually found a work around, but I thought it would be useful to be able to distinguish between the classic and the modern view. Thanks for your help.

@michael-amaya-bh michael-amaya-bh added the requires discussion This issues needs to be reviewed before development can start label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
requires discussion This issues needs to be reviewed before development can start
Projects
None yet
Development

No branches or pull requests

3 participants