Hashids.net
FluentValidation
Hashids.net | FluentValidation | |
---|---|---|
13 | 20 | |
3,253 | 8,787 | |
- | 0.8% | |
4.5 | 7.8 | |
6 months ago | 10 days ago | |
C# | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Hashids.net
-
Cache human-readable route-values of a Web API or not?
If you're just doing this to avoid Insecure Direct Object Reference (IDOR) problems, then perhaps something like Hashids might be a better choice?
-
Using a Guid as a PK, best practices.
I'm gonna be using this Library https://github.com/ullmark/hashids.net to encode the BIGINT into a string and decode the string back into the BIGINT within my web application.
-
Generating what appears to be a random long from a long, and being able to reliablely convert it back to its orignal value.
If you can use a string, then Markus Ullmark's hashids.net library would be a good place to start.
-
Does anyone know of a modern, DotNet7/C#10 implementation of this article, which covers tamper-proof hidden fields? They are exceedingly useful for CRUD forms which need to hold - but should never allow modification of - certain values, but I haven’t found an appropriate upgrade path.
You could use this approach along with this package https://github.com/ullmark/hashids.net
- Reversible "masking" of int data
-
Value converter of AutoMapper for hashids
Hashids helps you to convert a number Id to a string, this can make your app a little more secure hiding the actual id or related key of your DB when the data is requested by an API.
-
Is it ok to have sensitive data in cascading values?
Guids are nice, but there’s the option of hashids too. While it’s not advertised as a security mechanism, it does mask the integer and make things harder to guess
-
UUIDs to Prevent Enumeration Attacks
Another way to solve enumeration attacks is to use a two-way hashing algorithm to convert your auto-incrementing integer IDs to a hash of arbitrary length. This is essentially what YouTube is doing with their video IDs and it's a low-CPU, low-complexity solution that prevents/severely deters enumeration attacks.
Here is one such library for C# https://github.com/ullmark/hashids.net
- how to shorten the two-factor auth key?
-
[Parte 4] CQRS y MediatR: URLs seguros con HashIds
ullmark/hashids.net: A small .NET package to generate YouTube-like hashes from one or many numbers. (github.com)
FluentValidation
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
Here is an example of Command handler with built-in Fluent Validation and fire and forget style:
-
8 quick tips to improve your .NET API
There is an RFC called Problem Details (RFC7807) that standardizes how an error in an API should be responded to for the client. If you use Fluent validation, you may have noticed that the response is within this pattern.
- [Parte 2] CQRS y MediatR: Validando con FluentValidation
-
Building REST APIs In .Net 6 The Easy Way!
here we're defining the input validation requirements using fluent validation rules. let's see what happens when the user input doesn't meet the above criteria. execute the same request in swagger with the following incorrect json content:
-
How to properly sanitise & check POST data from REST API? Which libraries can you suggest? best ways nowadays in 2022
I remember FluentValidation being a nice library for this type of stuff.
-
Improving Anemic Models
Literally the code example in the front page: https://fluentvalidation.net/
-
BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
https://www.nuget.org/packages/Newtonsoft.Json/ https://www.nuget.org/packages/AutoMapper/ https://www.nuget.org/packages/Dapper/ https://www.nuget.org/packages/FluentValidation/ https://www.nuget.org/packages/FluentAssertions/ https://www.nuget.org/packages/NUnit/ https://www.nuget.org/packages/xunit/ https://www.nuget.org/packages/YamlDotNet/ https://www.nuget.org/packages/Moq/ That is simply not true. Mature c# projects purposely maintain no downstream dependencies and is they do, it's to a major reputable lib. See for yourself - these are staple third party packages commonly used. Anything dependency starting with System or NETStandard is Microsoft maintained.
- ASP.NET Core 6: Minimal APIs y Carter
-
GraphQL mutation union erros (6a) with Hotchocolate GraphQL Server
FluentValidator for validating and authorising certain fields.
-
Request Validation for Asp.NET API with Fluent Validation
Now that we know the importance of providing users with enough information about their requests and how it was processed, let’s focus on how we can configure our API to help us do that.One aspect of such meaningful experience is Request Validation (400 Error Range). For that purpose I am using a library called Fluent Validation.
What are some alternatives?
MediatR - Simple, unambitious mediator implementation in .NET
Guard - A high-performance, extensible argument validation library.
HidLibrary - This library enables you to enumerate and communicate with Hid compatible USB devices in .NET.
CsvHelper - Library to help reading and writing CSV files
Humanizer - Humanizer meets all your .NET needs for manipulating and displaying strings, enums, dates, times, timespans, numbers and quantities
ReactJS.NET - .NET library for JSX compilation and server-side rendering of React components
RecordParser - Zero Allocation Writer/Reader Parser for .NET Core
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
Enums.NET - Enums.NET is a high-performance type-safe .NET enum utility library