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.

Sign up for GitHub

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

Jump to bottom

feat: Schedule blog post #645

Merged
merged 2 commits into from
Oct 4, 2024
Merged

feat: Schedule blog post #645

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eb0b19c
feat: Schedule blog post
nzakas Oct 2, 2024
41bbdc3
Recategorize as Storytime
nzakas Oct 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...e-review-nit-to-ecosystem-improvements.md → ...e-review-nit-to-ecosystem-improvements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ teaser: "How implementing an ESLint rule led to changes in how people write Java
authors:
- captbaritone
categories:
- Case Studies
- Storytime
tags:
- Guest Post
- Rules
Expand Down Expand Up @@ -74,4 +74,4 @@ Each organization played a different, but key, role according to its strengths a

---

Thanks to [Brad Zacher](https://zacher.com.au/) for his initial key observation and ongoing encouragement, to [Nicholas C. Zakas](https://humanwhocodes.com/) and [Milos Djermanovic](https://github.com/mdjermanovic) for significant contributions to the rule during code review, and to [Ryan Cavanaugh](https://twitter.com/SeaRyanC) for bringing these same types of validation to the TypeScript ecosystem.
Thanks to [Brad Zacher](https://zacher.com.au/) for his initial key observation and ongoing encouragement, to [Nicholas C. Zakas](https://humanwhocodes.com/) and [Milos Djermanovic](https://github.com/mdjermanovic) for significant contributions to the rule during code review, and to [Ryan Cavanaugh](https://twitter.com/SeaRyanC) for bringing these same types of validation to the TypeScript ecosystem.