The new Prettier-based formatting commit hook is incompatible
with Windows CRLF line endings so enforce Unix LF everywhere.
The .gitattributes prior to this change causes these conversions even
if core.autocrlf is false. This configuration, in contrast, works
irrespective of the global git configuration. It also prevents files
from being committed with Windows line endings accidentally.
* Git 2.10 (release 2016-09-03) or later required
* Earlier versions of git will incorrectly apply eol=lf to binary
files unless explicitly called out as binary in .gitattributes
* Existing working copies on Windows will not have their existing line
endings corrected, and you will get `warning: CRLF will be replaced
by LF in <file>` when you edit them.
* To convert all of the files in an existing working copy to avoid
these warnings:
1. MAKE SURE all your work is committed and pushed somewhere as a
backup
2. MAKE SURE `git status` reports "nothing to commit, working tree
clean"
3. Run the following from working copy root:
```
git rm --cached -r .
git reset --hard
```
Pushing down methods from MessageReceiver that really only belong to StreamingReceiver. This is a prep-PR for a larger refactoring with StreamingReceiver but it's useful on its own.
Two breakages:
* A service side change has made it so specifying different values for sessionId and partitionKey is now considered a failure.
* Fix a broken test that got through when I accidentally skipped the live test run on my BatchingReceiverLite PR
Also, moved the receiverInit.spec.ts into 'internal' since it is purely a unit test.
As part of the ongoing enhancements to Track 2 we've been running into issues where code is getting duplicated between session and non-session (or worse, is drifting apart).
This PR is first in a series to unify the implementations, starting with unifying BatchingReceiver and MessageSession to the same body of code.
This is tangentially related to #9829, which will get the same treatment but for StreamingReceiver and MessageSession.
* [Text Analytics] Regenerating the SDK using the most recent version of swagger v3.0
* update release notes
* Update sdk/textanalytics/ai-text-analytics/CHANGELOG.md
Co-authored-by: Brian Terlson <brian.terlson@microsoft.com>
* Update sdk/textanalytics/ai-text-analytics/CHANGELOG.md
Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>
Co-authored-by: Brian Terlson <brian.terlson@microsoft.com>
Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>
* runtimeInfo replicas of eevent-hubs
* package.json entry for runtimeInfoBrowser
* move userAgent string to utils
* Update connContext and ATOMClient with userAgent
* Add user agent policy
* Update the link with the one Brian provided
* remove os shim
* Remove userAgent in the options since the userAgentPolicy covers it.
* remove TODO
* delete runtimeinfo files in favour of getPlatformSpecificData from core-http
* Revert "delete runtimeinfo files in favour of getPlatformSpecificData from core-http"
This reverts commit ef1c02ce42.
* update runtimeInfo files to be in sync with core-http
* make userAgent -> userAgentPrefix
* getDefaultUserAgentValue in userAgent
* getRuntimeInfo in userAgent for AMQP operations
* refactor ATOM client constructor for userAgent
* formatUserAgentPrefix helper
* Update API Report with UserAgentOptions
* Add userAgent in the options back again and some refactoring
* createPipelineFromOptions - use default pipeline policies
* revert os shim removal
* duplicated libInfo in user agent string
* remove shim by fixing the invalid file name
* Changelog
* remove @type {UserAgentOptions} in JSDocs
* Fix user agent string
* Do not set options.userAgent
Jeff Fisher
Nick Guerrera
Zachary Foster
Deyaaeldeen Almahallawi
Azure SDK Bot
Richard Park
Deyaaeldeen Almahallawi
Mitch Denny
Liang Wang
Mark Wolff
Daniel Rodríguez
Harsha Nalluru
Sarangan Rajamanickam
Orta Therox
Jose Manuel Heredia Hidalgo
chradek