feat: make side navigation bar work

[LiamTownsley2]

Resolves #20

[codacy-production]

ℹ️ Codacy found a minor Unused Code issue: 'partial' is gratuitous in this context.

The issue here is that the partial keyword is used when you expect to split the definition of a class, struct, or interface over two or more source files. It's a way of telling the compiler that other parts of this class, struct, or interface may be defined elsewhere. If you only have one part of the class, which seems to be the case here, the partial keyword is unnecessary and can be removed without affecting the functionality of the code.

Here's the code suggestion to fix the issue:

Suggested change

	public partial class StandardGenerator : UserControl
	public class StandardGenerator : UserControl

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Code Style issue: Remove this redundant 'ToCharArray' call.

The issue that SonarC# linter has pointed out is related to the unnecessary use of ToCharArray() when iterating over a string with a foreach loop. In C#, strings are already enumerable as they implement IEnumerable<char>, which means you can iterate over them directly without converting to a char array first.

Here's the code suggestion to fix the issue:

Suggested change

	foreach (char c in SYMBOLS.ToCharArray())
	foreach (char c in SYMBOLS)

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Code Style issue: Remove this redundant 'ToCharArray' call.

The issue that SonarC# linter has identified is that the ToCharArray() method call is redundant when iterating over a string with a foreach loop in C#. In C#, strings are already enumerable as a collection of char elements, so you can iterate over them directly without converting to a character array first.

Here's the code suggestion to fix the issue:

Suggested change

	foreach (char c in DIGITS.ToCharArray())
	foreach (char c in DIGITS)

---

This comment was generated by an experimental AI tool.

[codacy-production]

❌ Codacy found a critical Error Prone issue: Add a nested comment explaining why this method is empty, throw a 'NotSupportedException' or complete the implementation.

The issue identified by the SonarC# linter is that the label6_Click event handler method is empty. This could be intentional, but it is often the result of an auto-generated event handler that was never implemented. The linter suggests that you either provide an explanation as to why the method is intentionally left empty (using a comment), throw a NotSupportedException if the method should not be called, or implement the method's functionality if it is supposed to do something.

Since the requirement is to provide a single line change, I will add a comment explaining that the method is intentionally left empty. This is the simplest way to address the linter's concern without altering the behavior of the program.

Here's the code suggestion:

Suggested change

	private void label6_Click(object sender, EventArgs e)
	// This method is intentionally left empty. No action is required on label click.

---

This comment was generated by an experimental AI tool.

[codacy-production]

❌ Codacy found a critical Security issue: Add a 'default' clause to this 'switch' statement.

The issue here is that the switch statement does not have a default case. In C#, it's considered a best practice to include a default case in a switch statement. This ensures that there is a clear behavior for when none of the specified case labels match the value of the switch expression. Without a default case, if _ID doesn't match any of the provided case labels, the switch statement will do nothing, which might not be the intended behavior and could potentially lead to unpredictable outcomes.

Here's the suggested code change to add a default clause to the switch statement:

            default:
                break;

---

This comment was generated by an experimental AI tool.

[codacy-production]

⚠️ Codacy found a medium Security issue: Depending on the context, generating weak random numbers may expose cryptographic functions which rely on these numbers to be exploitable.

The security issue identified by Semgrep is related to the use of the System.Random class for generating random numbers that may be used in a cryptographic context. The System.Random class is not cryptographically secure, meaning that the numbers it generates are not unpredictable enough for cryptographic purposes. This can make the generated passphrases predictable and therefore vulnerable to attack.

To fix this issue, we should use a cryptographically secure random number generator such as System.Security.Cryptography.RandomNumberGenerator. Here's the line of code that needs to be changed to use a cryptographically secure random number generator:

Suggested change

	.Select(_ => wordList[rand.Next(wordList.Length)]));
	.Select(_ => wordList[RandomNumberGenerator.GetInt32(wordList.Length)]));

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Unused Code issue: 'partial' is gratuitous in this context.

The issue SonarC# linter is pointing out is that the partial keyword is unnecessary in the class definition because there is only one part of the PassphraseGenerator class. The partial keyword is used in C# when you want to split the implementation of a class, struct, or interface over two or more source files. When you have only one part of the class, the partial keyword serves no purpose and can be removed.

Here's the code suggestion to fix the issue:

Suggested change

	public partial class PassphraseGenerator : UserControl
	public class PassphraseGenerator : UserControl

---

This comment was generated by an experimental AI tool.

[codacy-production]

⚠️ Codacy found a medium Unused Code issue: Remove this unused method parameter 'separator'.

The issue identified by the SonarC# linter is that the separator parameter in the GetEmojis method is not being used anywhere within the method body. This means the parameter is unnecessary and can be removed to clean up the code.

Here's the code suggestion to fix the issue by removing the unused parameter:

Suggested change

	private static string[] GetEmojis(string separator)
	private static string[] GetEmojis()

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Unused Code issue: 'partial' is gratuitous in this context.

The issue that SonarC# linter is pointing out is that the keyword partial is unnecessary for the SelectType class definition. In C#, the partial keyword is used to indicate that the class, struct, or interface can be split across multiple files. However, if you do not have the class definition split and all parts of the class are contained within a single file, the partial keyword is redundant and can be removed.

To fix this issue, simply remove the partial keyword from the class definition. Here's the code suggestion:

Suggested change

	public partial class SelectType : Form
	public class SelectType : Form

---

This comment was generated by an experimental AI tool.

[codacy-production]

⚠️ Codacy found a medium Error Prone issue: Make 'CharacterList' 'readonly'.

The issue detected by the SonarC# linter is that the CharacterList field is not marked as readonly, but it appears to be intended as a field that should only be initialized once and not modified thereafter. Marking a field as readonly ensures that it can only be assigned during initialization or in the constructor of the class, which can help prevent bugs related to unintentional reassignment of the field after object construction.

Here is the code suggestion to fix the issue:

Suggested change

	private HashSet<string> CharacterList;
	private readonly HashSet<string> CharacterList;

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Code Style issue: Remove this redundant 'ToCharArray' call.

The issue highlighted by SonarC# is that calling ToCharArray() on a string when using a foreach loop is redundant because a string in C# already implements IEnumerable<char>. This means you can iterate over it directly without converting it to a character array first.

Here's the code suggestion to fix the issue:

Suggested change

	foreach (char c in LOWERCASE.ToCharArray())
	foreach (char c in LOWERCASE)

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Error Prone issue: Change return type to 'void'; not a single caller uses the returned value.

The issue that SonarC# linter has identified is that the CreatePassword method is defined to return a string, but based on the code snippet provided, it seems that none of the callers of this method actually use the returned string value. If this is indeed the case, the method's return type should be changed to void to reflect that it does not need to return anything.

However, it's important to note that the provided code snippet does not show the entire context. If the CreatePassword method is indeed meant to generate a password and return it to the caller, then the SonarC# linter's suggestion may be incorrect. Instead, the issue could be that the returned value is not being used where it should be, and the real fix would be to ensure that the returned password is utilized by the caller.

Assuming that the linter's assessment is correct and the return value is indeed not used anywhere, here is the code suggestion to change the return type to void:

Suggested change

	private string CreatePassword(int length)
	private void CreatePassword(int length)

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Code Style issue: Remove this redundant 'ToCharArray' call.

The issue here is that the ToCharArray method call is unnecessary because a string in C# can already be iterated over as a collection of characters. The foreach loop can operate directly on the string without converting it to a character array first. This redundant call to ToCharArray creates an unnecessary array and thus incurs a small performance penalty.

Here's the code suggestion to fix the issue:

Suggested change

	foreach (char c in stringToArray.ToCharArray())
	foreach (char c in stringToArray)

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Unused Code issue: Remove this redundant jump.

The issue identified by the SonarC# linter is that the return; statement at the end of the UpdatePasswordBox() method is redundant. In C#, if a method does not return a value (i.e., it's a void method), the return; statement is not needed to exit the method; the method will automatically return when the end of its code block is reached.

To fix this issue, simply remove the unnecessary return; statement:

Suggested change

	return;
	// Removed redundant return statement

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor Code Style issue: Remove this redundant 'ToCharArray' call.

The issue that the SonarC# linter has found is that the ToCharArray() method call is redundant when iterating over a string with a foreach loop. Strings in C# are enumerable, and you can iterate over them directly without converting them to a character array.

To fix this issue, you can simply remove the ToCharArray() call and iterate over the string directly. Here's the code suggestion to resolve the linter's complaint:

Suggested change

	foreach (char c in UPPERCASE.ToCharArray())
	foreach (char c in UPPERCASE)

---

This comment was generated by an experimental AI tool.