You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
🙃
implementing and fixing bugs
Michael Hladky
BioPhoton
🙃
implementing and fixing bugs
#Angular, #ionic, #RxJS, #TypeScript, #WebPerformance
Google Developer Expert
Microsoft MVP
push-based.io angular-vienna, angular-austria.at
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
Decision on message format in the deprecation documentation in code
As we need to decide on the message format (i.e. It's important if we focus on linter or docs),
I create a component that lets you test the message in many different places.
The information about a certain deprecation in the library also includes
the version when the breaking change will happen as well as code examples
for the usage before and after the deprecation.
This snippets are presented as highlited text in the migration timeline and also open up the code in StackBlitz.
To provide maintainable code examples we can use version range specifier to let StackBlitz automatically install new versions until the version of the breaking change.