Skip to content

Conversation

@Joseph2910
Copy link
Contributor

Description

Added required tag to variables if they contained the data annotation

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@github-actions
Copy link

github-actions bot commented Oct 2, 2025

Unit Test Results

✔️ Tests 855 / 855 - passed in 66s
📝 Coverage 57.02%
📏 4511 / 7776 lines covered 🌿 1085 / 2038 branches covered
🔍 click here for more details

✏️ updated for commit c831886

public string? MeshApiBaseUrl { get; set; }
[Required]
public string BSSMailBox { get; set; }
public required string BSSMailBox { get; set; }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have we made sure that the required decorator is the same as the required tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is the decorator checks in runtime and the keyword checks at compile time.

I think its safer if we check at compile time but keeping the decorator allows for nice config error messages

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We get the config at runtime though? Or have I misunderstood something?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think by having the required keyword it makes it easier and quicker to debug as functions will fail the healthchecks if they don't contain all the config

{
DemographicURI = "DemographicURI",
AllowDeleteRecords = allowDeleteRecords,
ParticipantManagementTopic = "ParticipantManagementTopic"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean this looks legitimate but, why are we adding all these here? Why were they not here before? Where have they come from? ahaha

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As on previous comment, the required keyword is compile time these values need to be set even though they are not used

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants