jeremymeng

The Storage SDK has been migrated to depend on the latest JavaScript core (v2) packages two years ago. We had to add a compatibility layer in order to avoid breaking changes in Storage public API surface. However, it adds additional maintenance cost, and Storage SDK remains an outlier because its API surface isn't consistent with the majority of our SDK packages. There are also patterns in the old autorest/swagger-based generator that we don't want carry forward to typespec-based generator. We are hoping to remove the compat layer and standardize Storage SDK packages so that their API surface is more aligned.

This document lists notable compatibility breaks if we remove the compat layer from, for example, @azure/storage-blob.

Client options

The option type passed to Client constructors will be different. Today customer can pass a StoragePipelineOptions option bag to a client constructor. After the changes they will pass a StorageClientOptions instead. The different options are:

• audience opti

olee

// create a bookmark and use this code as the URL, you can now toggle the css on/off
// thanks+credit: https://dev.to/gajus/my-favorite-css-hack-32g3
javascript: (function() {
	var styleEl = document.getElementById('css-layout-hack');
	if (styleEl) {
		styleEl.remove();
		return;
	}
	styleEl = document.createElement('style');
	styleEl.id = 'css-layout-hack';

dperini

//
// Regular Expression for URL validation
//
// Author: Diego Perini
// Created: 2010/12/05
// Updated: 2018/09/12
// License: MIT
//
// Copyright (c) 2010-2018 Diego Perini (http://www.iport.it)
//

banksean

/*
  I've wrapped Makoto Matsumoto and Takuji Nishimura's code in a namespace
  so it's better encapsulated. Now you can have multiple random number generators
  and they won't stomp all over eachother's state.
  
  If you want to use this as a substitute for Math.random(), use the random()
  method like so:
  
  var m = new MersenneTwister();