brunoblanes / average-crm Goto Github PK

It should connect straight with Creeper-bot so that he can open issues.

It should have top and side menus and the middle should be open for a default view to be defined.

Create a proper html email body for when the user confirms his account's email address.

Will need to add the DefaultLayout to the NotFound LayoutView in App.razor.

Might have something to do with the .NET Preview 7 SDK. Waiting for a reply from the .NET Team at https://github.com/dotnet/sdk/issues/12686

I want each user to have a unique email and username, but not have the username be its email address.

There's an open issue at the ASP.NET repo to investigate this.

CPF needs to be validated by the server and the client before creating a new entity.

Add all the default HTTP methods GET, PUT, POST and DELETE for all controllers.

Check to see if the following lines of code could be put into a static method given they apear, at least in some form, on more than three different pages.

// Generates the user account confirmation code
logger.LogInformation($"User {Email} created a new account with password.");
var code = await userManager.GenerateEmailConfirmationTokenAsync(user);
code = WebEncoders.Base64UrlEncode(Encoding.UTF8.GetBytes(code));
var callbackUrl = Url.Page(
	"/Account/ConfirmEmail",
	pageHandler: null,
	values: new { area = "Identity", userId = user.Id, code, returnUrl },
	protocol: Request.Scheme);

// Sends a confirmation email to the user
await emailSender.SendEmailAsync(Email,
	"Confirm your email",
	$"Please confirm your account by <a href='{ HtmlEncoder.Default.Encode(callbackUrl)}'>clicking here</a>.");

WASM: System.InvalidOperationException: Cannot provide a value for property 'AuthenticationStateProvider' on type 'Microsoft.AspNetCore.Components.Authorization.CascadingAuthenticationState'. There is no registered service of type 'Microsoft.AspNetCore.Components.Authorization.AuthenticationStateProvider'.

As of Entity Framework Core 5 Preview 8, TPT mapping is officially supported and I think it would be a better way to go forward.

Create a custom page for registering, logging in, logging out, etc. by Scaffolding from the Identity Library.

Web Api must accept JWT token from Xamarin Mobile apps and browsers.