Hey there! Right now, our encryption automatically goes for the Cipher Block Chaining (CBC) mode, we need to add a cool feature that allows users, pick the encryption mode that suits their needs.

the code below will generate an exception

var iv = KeyGenerators.GenerateRandomIVKeyAsString();
var secretKey = KeyGenerators.GenerateAesSecretKey(128);

//assigning values to the params
var encryptionParameters = new EncryptionParameters
{
DataToEncrypt = "YourDataToEncrypt",
IV = iv,
SecretKey = secretKey
};

var encryptionResult = await encryptor.EncryptToHexStringAsync(encryptionParameters);

The EncryptToHexStringAsync method needs to convert the IV key from Hex string to byte array

THE Cause of the error:
byte[] dataBytes = param.IV.ConvertKeysToBytes();

THE FIX: use the HexadecimalStringToByteArray() e=method to convert the IV to
byte[] dataBytes = param.IV.HexadecimalStringToByteArray();

Currently, there is a lack of a comprehensive suite of unit tests to validate the correctness of the encryption and decryption logic.

Implement robust error handling during encryption or decryption, including specific exceptions for different error scenarios, and provide meaningful error messages.

example:

try { // encryption or decryption algorithm here } catch (ArgumentNullException ex) { throw new ArgumentException("Invalid parameter. Ensure all parameters are not null.", ex); } catch (Exception ex) { throw new DecryptionException("Decryption failed. See inner exception for details.", ex); }

// catch IV key and secret key exception

`public class EncryptionException : Exception
{
public EncryptionException(string message, Exception innerException) : base(message, innerException)
{
}
}

public class DecryptionException : Exception
{
public DecryptionException(string message, Exception innerException) : base(message, innerException)
{
}
}`

There is no documentation (XML comments) for any of the methods in the codebase

The readme file is outdated and needs to be updated to show the new class name and how to use the encrypt methods for AES

refactor validator class to use a generic validation method instead of multiple validation

Alligning codes written to sonarqube's guidelines, Solid Principles etc.

We need to add asynchronous support to the encryption and decryption methods. This upgrade will allow users to leverage asynchronous programming patterns, making the whole process smoother and more responsive.

Readme and usage examples should also be updated to reflect this change