Fixed GetAccountInfoAsync deserialization

Author: JKorf

.gitignore

@@ -298,3 +298,4 @@ __pycache__/
 *.odx.cs
 *.xsd.cs
 *.nuspec
+Docs/

Binance.Net/Binance.Net.csproj

@@ -7,9 +7,9 @@
   <PropertyGroup>
     <PackageId>Binance.Net</PackageId>
     <Authors>JKorf, Nikkozp, CaptHolley</Authors>
-    <PackageVersion>7.2.6</PackageVersion>
+    <PackageVersion>7.2.7</PackageVersion>
     <AssemblyVersion>7.2.6</AssemblyVersion>
-    <FileVersion>7.2.6</FileVersion>
+    <FileVersion>7.2.7</FileVersion>
     <Description>Binance.Net is a .Net wrapper for the Binance API, including Binance Futures. It includes all features the API provides, REST API and Websocket, using clear and readable objects including but not limited to Reading market info, Placing and managing orders and Reading balances and funds</Description>
     <PackageRequireLicenseAcceptance>false</PackageRequireLicenseAcceptance>
     <PackageTags>Binance Binance.Net C# .Net CryptoCurrency Exchange API wrapper</PackageTags>
@@ -20,7 +20,7 @@
     <PackageLicenseExpression>MIT</PackageLicenseExpression>
     <NeutralLanguage>en</NeutralLanguage>
     <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
-    <PackageReleaseNotes>7.2.6 - Updated TransferType enum to match new API</PackageReleaseNotes>
+    <PackageReleaseNotes>7.2.7 - Fixed permission deserialization issue in GetAccountInfoAsync</PackageReleaseNotes>
   </PropertyGroup>
   <PropertyGroup Label="Deterministic Build" Condition="'$(Configuration)' == 'Release'">
     <PublishRepositoryUrl>true</PublishRepositoryUrl>

Binance.Net/Binance.Net.xml

@@ -322,6 +322,11 @@
             Leveraged account type
             </summary>
         </member>
+        <member name="F:Binance.Net.Enums.AccountType.TRD_GRP_002">
+            <summary>
+            See https://github.com/binance/binance-spot-api-docs/blob/master/rest-api.md#enum-definitions
+            </summary>
+        </member>
         <member name="T:Binance.Net.Enums.AccountUpdateReason">
             <summary>
             Account update reason

README.md

@@ -167,6 +167,9 @@ Yes, as long as the API endpoints are the same. Switch by changing the BaseAddre
 See Timestamping.
 
 ## Release notes
+* Version 7.2.7 - 29 Dec 2021
+    * Fixed permission deserialization issue in GetAccountInfoAsync
+
 * Version 7.2.6 - 09 Nov 2021
     * Updated TransferType enum to match new API