-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: added Why TypeScript Doesn't Follow Strict Semantic Versioning article #114
feat: added Why TypeScript Doesn't Follow Strict Semantic Versioning article #114
Conversation
…article Also adds a CaptionedImage component for the xckd comic within.
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.
heyyo :)
I really enjoyed the read, we've briefly talked about semver back with phaser's 404 page 😂 but I haven't thought much about it since (nor recalled the name).
And I now know something about TS's approach to versioning!
TBH, I don't feel like I did a thorough proofreading (it's a touch late) but I tried to provide broader feedback to the feel/messaging of the blog.
Hope this was helpful, thanks for sharing :)
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
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.
Hi @JoshuaKGoldberg. I gave some suggestions on how to improve your article. I might go back and do more, so stay tuned.
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Outdated
Show resolved
Hide resolved
src/content/articles/why-typescript-doesnt-follow-strict-semantic-versioning.mdx
Show resolved
Hide resolved
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.
Made some more suggestions
PR Checklist
Overview
Also adds a
CaptionedImage
component for the xckd comic within.