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

[gateway] assets fix and clear console warnings #1959

Merged
merged 7 commits into from
Jun 26, 2024

Conversation

Jennievon
Copy link
Contributor

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

  • update logo relative path for dark mode theme
  • change http-equiv to httpEquiv as React recognises the former as an Invalid DOM property
  • fix the fetch priority error: 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 lowercasefetchpriority instead.
    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

  • PR checks reviewed and performed

@Jennievon Jennievon requested a review from zkokelj June 11, 2024 13:09
@Jennievon Jennievon linked an issue Jun 11, 2024 that may be closed by this pull request
@Jennievon Jennievon changed the title Jennifer/1958 gateway assets fix [gateway] assets fix and clear console warnings Jun 11, 2024
Copy link
Contributor

@zkokelj zkokelj left a 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>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

I stil get those errors in console.

@@ -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"
Copy link
Contributor

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).

- logo relative path to cater to static files server
@Jennievon Jennievon force-pushed the jennifer/1958-gateway-assets-fix branch from 2ab57c3 to d747d6b Compare June 25, 2024 11:19
Copy link
Contributor

@zkokelj zkokelj left a 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.

@Jennievon Jennievon merged commit 0b01bfd into main Jun 26, 2024
2 checks passed
@Jennievon Jennievon deleted the jennifer/1958-gateway-assets-fix branch June 26, 2024 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gateway assets fix
2 participants