bldr | Awesome Task Runner - Simplified Build System/Task Runner | YAML Processing library

If you put the non-websnippet imports into an object:

While the builder pattern is useful, I think in this case it just complicates the straight-forward solution, although as you'll see, I'll present a couple that are more complicated, but those are based on increased performance optimizations on the first simple solution.

As you you noted, initializing and deinitializing classes is kind of slow. Actually the worst part is the dynamic memory allocation. Classes are powerful and definitely have their uses, but they're not the fastest tool in the Swift toolbox. Unless you make methods final, calling them can require a virtual dispatch. That can happen with protocols too depending on the particulars of their declaration, though in that case it's called "witness table thunking". But the worst part about classes is that their instances can be littered pretty much anywhere in memory. That's hell on the processor's on-chip cache. So for performance try to avoid dynamic dispatch, and reference types (ie, classes), and when you do need to allocate memory (such as Array or Dictionary), try to allocate all you need at once, and reuse it as much as possible. In Swift that requres some thought because of copy-on-write. You can easily end up allocating memory when you didn't intend to.

I present three solutions. Each one is more complicated, but also (hopefully) faster than the previous one. I'll explain why, and what to look out for. I should mention that I am not including the simplest solution. It is much like my first solution but with local variable arrays. The performance would not be especially good, and you're question makes it clear that performance is an issue.

First there's some boiler plate. To code it up and test it, I needed to define your Point and Line types, plus a few others I use for convenience, as well as some extensions purely for generating output. This code is common to all three solutions. Substitue your own definitions for Point and Line.

You should add UseTls and change DatabaseName like below:

According to CoinMarketCap API Plans, with free subscription you can use convert option for 1 currency per call only. Check out the error description you are getting back, you should see something like error_message: "Your plan is limited to 1 convert options".

Check the code here

1. For adding the line on bar chart, you can provide layer config as an array inside the spec object and provide multiple marks for it.
2. Similarly, add mark config with value text inside the layer. So, that will help to add the labels.
3. A similar pie chart is added at the bottom but the values of this pie chart is achieved by multiplying it with a value. For example: 5. The pie chart gets disappeared because it share the same axis or we can say theta config. To fix that you need to add a resolve config. Check the documentation for resolve config.
4. The selection configuration given in this tutorial has been added in the layer, where the mark bar is provided.
5. In vega or vega-lite, the data can be filtered using the transform config. Its use is somewhat similar to the calculate config which was used in your code. Check the documentation for filter transform.

Ignore (or [NotMapped] attribute) is definitely not for suppressing table generation. It basically is telling EF Core to not consider the class and it's properties as part of the model, hence it can't be used in LINQ to Entities queries and other EF Core provided services.

The only option to achieve your goal in EF Core 2.x is to map the SP result class as query type:

In addition to entity types, an EF Core model can contain query types, which can be used to carry out database queries against data that isn't mapped to entity types.

Query types have some limitations, but at the same time by default are not mapped to a database object, hence are perfect for using with FromSql.

All you need is to change the definitinion from DbSet to DbQuery:

I finally figured this out yesterday smh...I'm ashamed but the issue was that one of my Password model properties didn't match the ModelView Password in my API. Once they matched this worked fine...

Finally, found the solution. Turns out it was a stupid fault on my part. I accidentally mapped wrong streams and sinks to a wrong controller. In this case,

The interesting part of the error message is

None of the constructors found with Autofac.Core.Activators.Reflection.DefaultConstructorFinder on type EddiTools.Data.CalcRepository can be invoked with the available services and parameters:

Cannot resolve parameter EddiTools.Data.ICalcContext context of constructor Void .ctor(EddiTools.Data.ICalcContext).

which means Autofac tries to create a CalcRepository but no ICalcContext is available.

If you look at your registration, you only register the type without indicating it is a ICalcContext