If you use the great powershell-yaml module be aware. Version 0.4.8 released last Friday will break your code if you rely on case-insensitive property names.
If you use the great powershell-yaml module be aware. Version 0.4.8 released last Friday will break your code if you rely on case-insensitive property names.
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/
Well, given that I am about to perpetrate a #breakingchange I figure I should put some sort of versioning on #allthethings so that we can perform its #rollout with as few surprises as possible. I don’t know what order of #environments we will do (there may be some #nonproduction environments both before and after #production) but at least we will be able to track what knobs we turned and what levers we threw to get there. (Or rescue ourselves!)
If only it weren’t such a giant #chore.
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js files
I’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.
Heads up in case any of you are playing with Kitten¹, I’m going to implement a major API change today (it’s still pre-release/experimental so expect these things… though there should be fewer with time):
Instead of your routes receiving positional arguments like this:
export default (request, response) => { //… }
They will get a parameter object:
export default ({request, response}) => { //… }
Sådär! Då har jag deployat en #breakingChange i prod-miljön. #olidligSpänning #livetSomITKonsult