-
Notifications
You must be signed in to change notification settings - Fork 38
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
[gateway] assets fix and clear console warnings #1959
Conversation
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.
It doesn't fix things for me. If you want we can check that together.
@@ -25,9 +25,9 @@ const HeadSeo = ({ | |||
signature="_vd3udx2g2hfn9zclob5cat43b94q7fyk" | |||
></meta> | |||
{/* SECURITY: to prevent the page from being loaded in an iFrame */} | |||
<meta http-equiv="X-Frame-Options" content="deny"></meta> | |||
<meta httpEquiv="X-Frame-Options" content="deny"></meta> |
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.
@@ -14,7 +14,7 @@ export default function Header() { | |||
<div className="flex h-16 justify-between items-center px-4"> | |||
<Link href="/"> | |||
<Image | |||
src="/static/assets/images/black_logotype.png" | |||
src="/assets/images/black_logotype.png" |
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.
logos are now broken in both white and black version.
I run: npm run build and then serve static files with golang (same way as then deployed to Azure).
…nnifer/1958-gateway-assets-fix
2ab57c3
to
d747d6b
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.
LGTM.
I would also remove:
since it is reporting an error in console and since it is incorrect way to do this it is not protecting us at all.
Why this change is needed
Please provide a description and a link to the underlying ticket
#1958
What changes were made as part of this PR
Please provide a high level list of the changes made
http-equiv
tohttpEquiv
as React recognises the former as anInvalid DOM property
Warning: React does not recognize the
fetchPriorityprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase
fetchpriorityinstead.
this occured because there was a bug in the next package version and the bug has been fixed but we needed to update the package version too
PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks