binder | Android binder example | Form library

I was trying to use the new DateOnly type in .NET 6, but I had trouble with the model binding. A perfectly normal form data such as this:

was parsed to "0001.01.01" and accepted as valid by the binder.

Replacing all DataOnly with the good old DateTime instantly solved this issue.

Could this be a bug in the BCL or am I missing some intentions here? Is there any workaround except for implementing a custom model binder?

As of .NET 6 in ASP.NET API, if you want to get DateOnly (or TimeOnly) as query parameter, you need to separately specify all it's fields instead of just providing a string ("2021-09-14", or "10:54:53" for TimeOnly) like you can for DateTime.

I was able to fix that if they are part of the body by adding adding custom JSON converter (AddJsonOptions(o => o.JsonSerializerOptions.Converters.Add(...))), but it doesn't work for query parameters.

I know that could be fixed with model binder, but I don't want to create a model binder for every model that contains DateOnly/TimeOnly. Is there a way to fix this application wide?

Demo:

Lets assume you have a folowwing action:

[HttpGet] public void Foo([FromQuery] DateOnly date, [FromQuery] TimeOnly time, [FromQuery] DateTime dateTime)

Here's how it would be represented in Swagger:

I want it represented as three string fields: one for DateOnly, one for TimeOnly and one for DateTime (this one is already present).

PS: It's not a Swagger problem, it's ASP.NET one. If I try to pass ?date=2021-09-14 manually, ASP.NET wouldn't understand it.

I have configured my producer as :

I'm trying to create a C++ Jupyter Notebook using xeus-cling and mybinder. I wanted to include the library armadillo and I was able to do that locally in a Jupyter Notebook as follows:

we are currently trying to implement a non-critical validation layer that checks field inputs against certain validators without marking the form as "not valid", but rather as "out of specification" so that we can highlight the fields to the user. In particular we are talking about number ranges with lower and upper boundaries that should highlight the input fields as some sort of "out of specification" warning. The input itself is considered valid but "out of specifaction" while the user should still be able to save the data.

Here's an example:

• allowed input of any integer (validation), with an input specification of integers between 90 and 100 (specification).
• input "abc" -> wrong input type -> error message, saving not allowed
• input "95.1234" -> wrong input type -> error message, saving not allowed
• input "85" -> correct input type, valid input, but out of specification -> warning message, saving still allowed
• input "95" -> correct input type, valid input, in specification -> saving allowed

This means the normal binder validation should still block the saving while the additional non-critical validation should just highlight it, but not block it.

We are currently using the vaadin binder in vaadin version 14 and are using the features of converters and validators. Is there a possibility to add our layer to the vaadin binder so that it performs fluently with our current usage? Or do we have to build our own non-critical validation layer additionally to the normal vaadin binder usage? In an ideal world we would pin it after conversion and validation phase:

1. field input
2. type conversion
3. critical validation
4. non-critical validation
5. input saving

I hope my description is sufficient. If there are any questions, just let me know and I try to describe it a little bit more detailed. Thanks in advance.

I'm upgrading a Spring Boot application to Boot 2.6.1, Cloud 2021.0.0 and Cloud Stream 3.2.1.

This application has a bunch of KStreams such as:

This is regarding vulnerability reported with CVE-2021-44228 against the log4j-core jar and has been fixed in Log4J v2.15.0.

We use Logback API via slf4j. This is confirmed with below code.

I recently noticed that my live wallpaper apps are crashing when users try to set the newly introduced "Theming Icons" functionality on Android 12. This new functionality calculates a palette of colors from the user's current static wallpaper and uses this palette to color some of the other apps icons (a feature of the new "Material You" design). But for some reason when it operates on a live wallpaper it crashes the app with the following log:

The Background:

1. Consuming application is a website built using .NET Core 3.1.
2. Consuming application references a NuGet package built using .NET Standard 2.0.
3. The consuming application has a reference to the latest version of the NuGet package and builds without any errors or warnings.
4. The DLL from the NuGet package is visible in the bin\debug\netcoreapp31\ and bin\release\netcoreapp31\ folders.
5. In the IDE, full IntelliSense for the types in the NuGet package is available, including the XML Documentation comments for types, methods, and parameters.
6. At runtime, at the first reference to any type in the NuGet package, a FileNotFound exception is thrown, reporting that the DLL from the NuGet package file cannot be found.

What I have tried:

1. Verifying that the PackageReference entries in the .csproj file is correct. Since it's a .NET Core application, there are no hint paths or assembly binding redirects that are interfering with assembly binding.
2. Clearing the NuGet cache.
3. Removing and re-adding the NuGet package.
4. Forcing NuGet to reinstall the package through the Package Manager Console.
5. Cleaning and rebuilding the solution.
6. Enabling Fusion Log Viewer and combing through the logs. This is where things get interesting. There are no entries in the logs indicating any attempts to resolve or load the assembly, or any entries indicating that the assembly bind failed.

Exception Message