-
Notifications
You must be signed in to change notification settings - Fork 0
feat: adding search #828
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
Open
kaltepeter
wants to merge
4
commits into
main
Choose a base branch
from
updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: adding search #828
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| import { Chip, ListItem, ListItemText, Typography } from "@mui/material"; | ||
| import { styled } from "@mui/material/styles"; | ||
| import { Link } from "gatsby"; | ||
| import React from "react"; | ||
| import { Note } from "../models/note"; | ||
|
|
||
| const NoteItemContainer = styled(ListItem)({ | ||
| "& .head": { | ||
| display: "flex", | ||
| justifyContent: "space-between", | ||
| alignItems: "baseline", | ||
| }, | ||
| }); | ||
|
|
||
| const TagList = styled("ul")(({ theme }) => ({ | ||
| display: "flex", | ||
| justifyContent: "left", | ||
| flexWrap: "wrap", | ||
| listStyle: "none", | ||
| padding: theme.spacing(0.5), | ||
| margin: 0, | ||
| })); | ||
|
|
||
| const TagChip = styled((props: React.ComponentProps<typeof Chip>) => ( | ||
| <Chip component="span" {...props} /> | ||
| ))({ | ||
| border: "none", | ||
| borderRadius: 0, | ||
| }); | ||
|
|
||
| type NoteListEntryProps = { | ||
| note: Note; | ||
| titleComponent?: "h2" | "h3"; | ||
| }; | ||
|
|
||
| const NoteListEntry: React.FC<NoteListEntryProps> = ({ | ||
| note, | ||
| titleComponent = "h3", | ||
| }) => ( | ||
| <NoteItemContainer divider> | ||
| <ListItemText | ||
| inset={false} | ||
| slotProps={{ | ||
| primary: { className: "head" }, | ||
| secondary: { component: "div" }, | ||
| }} | ||
| primary={ | ||
| <> | ||
| <Typography component={titleComponent} variant="h6"> | ||
| <Link to={note.fields.slug}> | ||
| {note.frontmatter.title} | ||
| </Link> | ||
| </Typography> | ||
| <Typography variant="overline">{note.frontmatter.date}</Typography> | ||
| </> | ||
| } | ||
| secondary={ | ||
| <> | ||
| <TagList> | ||
| {note.frontmatter.tags?.map((tag) => ( | ||
| <Typography component="li" variant="subtitle1" key={tag}> | ||
| <TagChip | ||
| size="medium" | ||
| variant="outlined" | ||
| color="secondary" | ||
| label={`#${tag}`} | ||
| /> | ||
| </Typography> | ||
| ))} | ||
| </TagList> | ||
| <Typography component="p" variant="body1" color="text.primary"> | ||
| {note.excerpt} | ||
| </Typography> | ||
| </> | ||
| } | ||
| /> | ||
| </NoteItemContainer> | ||
| ); | ||
|
|
||
| export default NoteListEntry; |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Bumping the supported Node engine from
>=18.16.1to>=24.15.0is a major operational change and is significantly stricter than what Gatsby 5 itself declares (it supports>=18 <26per the lockfile). If the project truly requires Node 24.15 specifically (vs 24.x / >=24), it would help to justify this in the PR or relax it to the minimum actually required so CI/deploy environments don’t break unnecessarily.