Feature/api v152

[stashjones]

No description provided.

[codacy-production]

❌ Codacy found a critical Error Prone issue: Use the overloading mechanism instead of the optional parameters.

The issue identified by the SonarC# linter is related to the use of optional parameters in the method signature. The linter suggests that instead of using optional parameters, which can lead to ambiguity and make the method less clear, it is better to use method overloading to provide different versions of the method for different parameter sets.

To resolve this issue, you can create an overloaded version of the GetOrganizationFloorPlansAutoLocateDevicesAsync method without the cancellationToken parameter. The original method can then call this overloaded version, providing a default value for the cancellationToken.

Here’s the suggested one-line change to implement the overload:

Suggested change

	CancellationToken cancellationToken = default);
	Task<FloorPlansAutoLocateDevices> GetOrganizationFloorPlansAutoLocateDevicesAsync(string organizationId);

This change would require you to implement the overload in the same class, ensuring that the original method still functions as intended.

---

This comment was generated by an experimental AI tool.