This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Create Development Kitchen #963
Merged
Merged
Changes from 11 commits
Commits
Show all changes
31 commits
Select commit
Hold shift + click to select a range
edcb038
rename editorial directory to kitchen
552f931
remove web, ios and android folders from kitchen
d95cb6f
rename editorial package to source-kitchen-react
67fdd25
reset source-kitchen-react version to 0.0.1
66fff46
Update workspace config for kitchen
9601f3f
remove individual package.json files in kitchen
c1dfa5b
remove individual tsconfig.json files in kitchen
ead59ef
Rename starRating to star-rating
006bf57
update kitchen index.tsx
dcaf0c9
Update component READMEs to point to source-kitchen-react npm package
4982713
update kitchen storybook titles
703dff0
Update the kitchen README
a68b66e
update scripts for kitchen
80686d4
add release process for kitchen
52eb675
add kitchen to autolabeler
f70d3f5
Move @guardian/types to be dev and peer dep
a9304bd
bump version of @guardian/types
43c53c6
Update story titles
c9f8e8a
Remove kitchen script from package.json
2c4e56e
Update src/kitchen/README.md
3be6657
Apply suggestions from code review
d078e7f
add contributing guidelines for dev kitchen
SiAdcock 484cd8c
set dotcom-platform as codeowners of all current kitchen components
SiAdcock 4b7cdf5
reinstate kitchen workspace scripts
SiAdcock e6836b3
make package naming consistent
SiAdcock 1868179
explicitly export components and prop types for each component
SiAdcock d1243af
Update kitchen package name
02cbc27
Move kitchen to packages/@guardian/source-react-components-developmen…
acbcc1e
Merge branch 'main' into development-kitchen
24cf88b
Pass count arg as string in stories
c3391a0
rename button to editorial button
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
There are no files selected for viewing
This file contains 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
Empty file.
Empty file.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
File renamed without changes.
This file contains 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
File renamed without changes.
This file contains 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
File renamed without changes.
This file contains 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
File renamed without changes.
File renamed without changes.
File renamed without changes.
6 changes: 3 additions & 3 deletions
6
...al/web/components/lines/Lines.stories.tsx → ...itchen/components/lines/Lines.stories.tsx
This file contains 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
File renamed without changes.
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.
Does this component now need to be called something else (e.g.
EditorialButton
) as we can't use the package name to differentiate it from the standard SourceButton
?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.
@guardian/dotcom-platform what do you think?
EditorialButton
PillarButton
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.
Adding an option:
ThemeButton
?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.
Thanks @oliverlloyd I personally think the word
Theme
is already used more generally to support, for example, the various Reader Revenue themes and the brand themes (see Figma). Do you see Theme as something specific to Format?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.
Format.Theme
is a superset ofPillar
which also includesLabs
andSpecialReport
https://github.com/guardian/libs/blob/main/src/format.ts#L16
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.
In the migration to
@guardian/libs
,Format
becomesArticleFormat
. In fact everything related toArticleFormat
gets anArticle
prefix. Maybe we should reflect that in Source too, withArticleButton
?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.
Wasn't it that
ArticleFormat
is named such because it specifically relates to articles? With the thinking being you would later have aContainerFormat
(orSliceFormat
,SectionFormat
?) which represents Fronts.SectionFormat
would contain and array of articles which each haveArticleFormat
.I mention this because I don't think the same model exists for a button. They can be used everywhere in the editorial space and have a much simpler design pattern, one not limited to articles.
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.
On the other hand, if we follow this thinking through, you'd have
where
myFormatObject
would be typed asArticleFormat
. So if you can only ever pass inArticleFormat
then maybeArticleButton
works?🤷
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.
Good thoughts @oliverlloyd. I guess the
format
prop could expect something that's either anArticleFormat
orContainerFormat
But I think you're right in that<EditorialButton>
better reflects the context in which this button can be used.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.
I've renamed to EditorialButton unless anyone has any last minute alternatives