Localizer | Package based Terraria mod localization manager

I had RootNamespace element set in .csproj, by removing the element, I removed the issue.

Adding the selectable prop means that users can use the mouse to click and drag in order to select a range of times. The slots array will not give you all the events for the day, or for the selected range - rather, it'll give you just the selected range.

If you click on a day, the (only) value in the slots array will be the Date corresponding to the start of the day. You can use the start and end properties to see when the day starts and when it ends (exclusive).

If you click and drag, the slots array will contain all timeslots dragged over, where the duration of a timeslot is determined by the steps prop.

If you want to get a list of all elements for a particular day when the day is clicked, you can either filter out the events that don't match inside the onSelectSlot callback, or to pass down event objects that contain a reference to an array containing all events for that day. It does require a tiny bit of code on your part, but that's nothing to be afraid of.

I found the answer on the github discussion:

https://github.com/bUnit-dev/bUnit/discussions/239

You only specified an English localization file: Shared.en.resx.

When you specify @loc["countries"] in the component, it attempts to use the browser locale to translate the text "countries".

The localizer looks for a resource file Shared.de.resx but that doesn't exist, so it defaults to the base translation, in this case English.

I used regex to split the source at the tokens configured in TokenMappings. Token mappings could easily be loaded from a json source for example. To configure more "{markings}" just add more lines to the TokenMappings.

I found the issue, turns out that way I was reading the file was causing an issue, that after many attempts we depicted the faulty code and replace it for this:

My usual approach is to put all the query-building code in my repositories, and have them return a materialized result. So I can mock the repository layer when unit-testing my services class.

Trying to unit-test the data access layer can be fraught, since it's inherently designed to be an integration layer. Queries that work one way when you are using in-memory objects may have different behavior when they're translated by Entity Framework.

If you prefer building your queries in the service layer, Ian Kemp's approach can work, basically putting your ConvertToListAsync method into the EfRepository class and its interface instead of having a whole new service to inject.

By https://blazorise.com/docs/components/grid/

you can just use gutter. Modify your opening Row tag to look like this for example:

Change #1 is irrelevant, since it's just fixing the Misuse - Longrunning Operations Under async Methods:

We noticed that developers use some potentially long running operations under async methods even though there are corresponding asynchronous versions of these methods in .NET or third-party libraries.

or in simple words, inside async method use library async methods when exist.

The change #2 and #3 though are incorrect. Looks like you are trying to follow the Misuse - Unnecessary async Methods:

There are some async methods where there is no need to use async/await. Adding the async modifier comes at a price: the compiler generates some code in every async method.

However, your method needs async/await, because it contains a disposable scope which has to be kept until the async operation of the scoped service (in this case db context) completes. Otherwise the scope exits, the db context is disposed, and no one can say what happens in case SaveChangesAsync is pending at the time of disposal - you can get the error in question, or any other, it's simply unexpected and the behavior is undefined.