dailybruin / lux Goto Github PK

We currently only support one credit for each one - it may be useful to add an optional string parameter for legacy posts and custom photo illos

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	react-testing-library
npm	travis-deploy-once
npm	tslint
npm	tslint-react

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update dependency docz to v2
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency semantic-release to v24
• chore(deps): update dependency tslint to v6
• chore(deps): update dependency tslint-react to v5
• chore(deps): update dependency webpack to v5
• chore(deps): update react monorepo to v18 (major) (@types/react, @types/react-dom, react, react-dom)
• fix(deps): update dependency d3 to v7
• fix(deps): update dependency react-helmet to v6 (react-helmet, @types/react-helmet)
• fix(deps): update dependency react-string-replace to v1
• fix(deps): update dependency typescript to v5
• fix(deps): update font awesome to v6 (major) (@fortawesome/fontawesome-svg-core, @fortawesome/free-solid-svg-icons)

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• fix(deps): update dependency react-emotion to v10
• fix(deps): update emotion monorepo to v11 (major) (emotion, emotion-server, jest-emotion)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update all non-major dependencies (@fortawesome/fontawesome-svg-core, @fortawesome/free-solid-svg-icons, @fortawesome/react-fontawesome, @mdx-js/react, @types/jest, @types/react, @types/react-dom, @types/react-helmet, @types/webfontloader, commitizen, d3, docz, gatsby, lint-staged, plyr, react, react-dom, react-player, react-string-replace, react-testing-library, semantic-release, slugify, tslint, tslint-config-prettier, typescript, webpack)
• chore(deps): update dependency @mdx-js/react to v3
• chore(deps): update dependency commitizen to v4
• chore(deps): update dependency cz-conventional-changelog to v3
• chore(deps): update dependency react-testing-library to v8
• chore(deps): update gatsby monorepo (major) (gatsby, gatsby-plugin-emotion)
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

test issue from slack!

Description

When using Lux with Gatsby to compile to HTML, it fails on the use of document and window since these are not present on SSR (server-side rendering)

So we can centralize these and not have to rewrite them every time

planned: mainsitearticleheader uses a ton of links with

text-decoration: none;
                color: ${dailyBruinBlue};

                :hover {
                  opacity: 0.75;
 }

We can refactor this into a MainSiteLink component - because link behavior and appearance in body text should be consistent across the entire site to promote good UX

Article cards come in these three variants. They should have a section category, headline, byline, photo and blurb

On registry https://registry.npmjs.org/, the "latest" version (v5.0.11) of dependency travis-deploy-once has the following deprecation notice:

We recommend to use Travis Build Stages instead

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about travis-deploy-once's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

This is a little more involved and may require a microservice backend

Add a navbar which will stick to the top of the page and will hold links that jump to other pages (Gatsby Link) on the site or id's on the same page (and potentially external links?)
Have a style prop to allow for custom css, keep the css minimal as a base.

An idea for the links prop is an array of objects with the structure:

{
    title: string, // what shows up in the nav bar
    targeturl: string, // where the link points to
    type: string // declaring the link as external, internal, or id, could make this an enum
}

You could forgo the type key and have the navbar figure out internally what type of link it is (# at the front for ids, http at the front for external links) but I think declaring it is the better way to go.

This is just a suggestion, comment for a better solution and we can work it out.

Don't know how much value this adds to a project

ARTS BOX - example at https://dailybruin.com/2018/10/05/album-review-twenty-one-pilots-trench-falls-flat-fails-to-produce-a-variety-of-sounds/
Needs

• Review title (required)
• Custom Line 1 (optional)
• Custom Line 2 (optional)
• Date (required)
• Rating (out of 5) (required)

SPORTS BOX - example at http://dailybruin.com/2018/11/05/womens-volleyball-defeats-oregon-state-falls-to-oregon/

• Sport name (required)
• Team 1 (required)
• Team 2 (required)
• Team 1 score (required)
• Team 2 score (required)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Editors picks + popular stories are essentially the same thing

• we can return 3 links for each card
• each link should have a title and a blurb
• editors picks additionally has a photo at the top related to the first link

We should be able to add custom css to lux components. This should be done through an additional style prop that takes a string.

An example to look would look like this:

<Image
  url="http://dailybruin.com/images/2018/10/web.sp_.mwp_.nbk_.ADX_-640x461.jpg"
  caption="Freshman attacker Ashworth Molthen has registered 21 goals on the season, finding the back of the net in 13 of the 16 games so far this year for UCLA men’s water polo. UCLA is one of two teams remaining in the MPSF conference that remains undefeated."
  credit="Amy Dixon/Photo editor"
  alt="Ashworth Molthen playing water polo."
  style={css`
    color: red;
  `}
/>

You'll want to check out the emotion docs on composition.

It's a tad too small right now - 0.9em would probably work best

Trying to use Lux footer inside the main site app but running into an issue where webfontloader leads to a compilation issue.