Release: v6.1.0

[adrianhall]

What's Changed

• (#873) Adjust EntityTableRepository so that it can be inherited. by @adrianhall in (#873) Adjust EntityTableRepository so that it can be inherited. #884
• (#882) Update NSwag to v14.0.2 by @adrianhall in (#882) Update NSwag to v14.0.2 #885
• (#883) Expose the underlying HttpClient for the service connection. by @adrianhall in (#883) Expose the underlying HttpClient for the service connection. #887
• (#886) Convert InMemoryRepository to use ConcurrentDictionary by @adrianhall in (#886) Convert InMemoryRepository to use ConcurrentDictionary #888
• (#877) Add IN support for Remote Tables by @adrianhall in (#877) Add IN support for Remote Tables #892

Full Changelog: 6.0.8...6.1.0

---

This discussion was created from the release 6.1.0.

[adrianhall]

Hey folks - releasing v6.1.0 - this has a couple of breaking changes in it, especially around the EntityTableRepository visibility.

EntityTableRepository can now be inherited!

This means you can override just the methods you want. The basic ones to deal with are GetEntityAsync() and AsQueryable(). This allows you to do things like this:

public class MyRepository : EntityTableRepository<MyEntity>
{
  protected overide Task<TEntity> GetEntityAsync(string id, CancellationToken token = default)
    => DataSet.Include(x => x.Permissions).AsNoTracking().SingleOrDefaultAsync(x => x.Id == id, token);
}

Which, in turn, makes it easier to do permission checks in your access control provider.

There is a HttpClient for you to use

You can now use client.HttpClient to get access to the underlying HttpClient that the DatasyncClient is using to communicate with the service. This includes the pipeline and authentication requirements. Note that if you just want to use .SendAsync(), you can do that on the client. However, if you want to use extension methods like PostAsJsonAsync(), then the client is available to you.

You can use string[].Contains(string) in Where clauses on remote tables

I've added the OData generation for IN support, which supports things like this:

var ratings = new string[] { "G", "PG", "PG-13" }
var items = await remoteTable.Where(x => ratings.Contains(x.Rating)).ToListAsync();

This is translated into ODATA $filter=rating IN ('G','PG','PG-13'). However, this only works for REMOTE tables. Offline tables will not have this facility until the next release (or the DbContext version I'm planning in v8), so it's best used to restrict what data is brought down from the server rather than for doing queries.

I've made the InMemoryRepository thread-safe

The InMemoryRepository used to use Dictionary<string,TEntity> to store the data in-memory. I've moved it over to using ConcurrentDictionary<string,TEntity> instead. This has improved stability in tests.

NSwag support has been updated to v14.0.2

If you are using NSwag, make sure you update your NSwag.AspNetCore library version! The v14 NSwag library comes with a bunch of new issues that are not related to Azure Mobile Apps, so make sure the problem you are experiencing is with the code in Azure Mobile Apps before opening an issue, please. I don't have time or the expertise to be debugging NSwag issues.

This is not a required update, so feel free to continue using 6.0.8 if it works for you!