New Task Frends.Opcua.Write#7
Open
RikuVirtanen wants to merge 10 commits into
Open
Conversation
|
Warning Review limit reached
More reviews will be available in 28 minutes and 41 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThis PR adds the Frends.Opcua.Write task: DTOs/enums, validation attributes, connection/session management, core Write implementation, test infrastructure (Docker + certs), functional and unit tests, project/packaging metadata, and CI workflows for testing and release. ChangesFrends.Opcua.Write Task Implementation
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 18
🧹 Nitpick comments (3)
Frends.Opcua.Write/Frends.Opcua.Write/Helpers/ErrorHandler.cs (1)
26-29: ⚡ Quick winPreserve original stack trace when rethrowing cancellation.
Line 28 uses
throw exception;, which resets the stack trace. UseExceptionDispatchInfo.Capture(exception).Throw()for accurate diagnostics.Suggested fix
+using System.Runtime.ExceptionServices; using System; using Frends.Opcua.Write.Definitions; @@ private static void ThrowIfCanceled(Exception exception, bool throwCanceled = true) { - if (throwCanceled && exception is OperationCanceledException) throw exception; + if (throwCanceled && exception is OperationCanceledException) + ExceptionDispatchInfo.Capture(exception).Throw(); }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Frends.Opcua.Write/Frends.Opcua.Write/Helpers/ErrorHandler.cs` around lines 26 - 29, The ThrowIfCanceled method currently rethrows OperationCanceledException using "throw exception;" which resets the stack trace; update ThrowIfCanceled(Exception exception, bool throwCanceled = true) to rethrow via ExceptionDispatchInfo.Capture(exception).Throw() (and ensure the appropriate using for System.Runtime.ExceptionServices is added) so the original stack trace is preserved when exception is an OperationCanceledException and throwCanceled is true.Frends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.cs (1)
3-3: ⚡ Quick winAdd an explicit
Newtonsoft.Jsonpackage reference (avoid relying on transitive dependencies).
Frends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.cs(and other files in this repo) useusing Newtonsoft.Json.Linq;, but none of the projects’.csprojfiles include a directPackageReferencetoNewtonsoft.Json—so the build depends on whatever transitive package currently brings it in.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Frends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.cs` at line 3, The project relies on Newtonsoft.Json via transitive dependencies but files like ValidJsonArrayAttribute.cs (class ValidJsonArrayAttribute) reference Newtonsoft.Json.Linq directly; add an explicit PackageReference for Newtonsoft.Json to the project that contains ValidJsonArrayAttribute (and any other projects that directly use Newtonsoft.Json types) in its .csproj so the build does not rely on transitive packages, then run dotnet restore / rebuild to verify resolution.Frends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.cs (1)
68-68: ⚡ Quick winRemove debug artifacts from the test code.
Line 68 contains commented-out path code, and Lines 149-152 print diagnostic output to console. These should be removed to keep tests clean and stable in CI logs.
Suggested change
- PrivateKeyPath = string.Empty, // Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "../../../Volumes/trusted-user/certs/user.key"), + PrivateKeyPath = string.Empty, @@ - Console.WriteLine($"Volumes dir: {connectionSecure.CertificatePath}"); - Console.WriteLine($"Absolute path: {Path.GetFullPath(connectionSecure.CertificatePath)}"); - Console.WriteLine($"Volumes exists: {Directory.Exists(connectionSecure.CertificatePath)}");As per coding guidelines,
Frends.*/**/*.cs: Clean structure and no unused code.Also applies to: 149-152
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Frends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.cs` at line 68, Remove the debug artifacts from the FunctionalTests class: delete the commented-out hardcoded path fragment from the PrivateKeyPath assignment (the commented Path.Combine line next to PrivateKeyPath = string.Empty) and remove the diagnostic Console.WriteLine calls printed in the test (the console output around lines 149–152) so the test contains no commented-out test paths or transient diagnostic prints; keep the PrivateKeyPath set to string.Empty and ensure no other references to the removed debug prints remain in the FunctionalTests class.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/Write_release.yml:
- Line 10: The workflow references a reusable workflow with a mutable ref
("FrendsPlatform/FrendsTasks/.github/workflows/release.yml@main"); replace the
mutable branch ref `@main` with an immutable commit SHA for that reusable workflow
(i.e., change the ref after the `uses:` entry to the specific commit SHA) so the
action is pinned to a single commit and cannot change unexpectedly.
In @.github/workflows/Write_test_on_main.yml:
- Line 15: The workflow reference currently pins to a mutable branch in the line
using "uses:
FrendsPlatform/FrendsTasks/.github/workflows/linux_build_main.yml@main"; replace
the "`@main`" suffix with a vetted commit SHA for that repository (e.g.
"@<commit-sha>") to pin the reusable workflow, and update any other occurrences
of ".../workflows/*`@main`" in this file to the appropriate vetted SHAs so the
referenced reusable workflows are immutable and reproducible.
In @.github/workflows/Write_test_on_push.yml:
- Line 15: The workflow currently references a reusable workflow using a mutable
ref ("uses:
FrendsPlatform/FrendsTasks/.github/workflows/linux_build_test.yml@main" in the
build job); replace the mutable ref `@main` with an immutable commit SHA of the
referenced repository (the exact commit that matches the intended workflow
version) so the build job's reusable workflow is pinned and CI is reproducible,
and update that SHA whenever you intentionally upgrade the reusable workflow.
In `@Frends.Opcua.Write/CHANGELOG.md`:
- Around line 3-7: Replace the vague "- Initial implementation" entry under "##
[1.0.0] - 2026-05-22" / "### Added" with a bulleted list of concrete,
user-visible features (e.g., "Added OPC UA write task with single/multi-node
support", "Supported auth modes: Anonymous, Username/Password, Certificate",
"Input validation for node ids and value types", "Retry/backoff behavior and
error semantics", "Test infrastructure: integration tests + CI job"), and add an
"### Changed" or "### Fixed" section if applicable plus an "### BREAKING
CHANGES" or "Upgrade notes" subsection describing any config or API changes
users must perform; ensure the document follows Keep a Changelog style (dateed
header, categorized sections) and replace the original "- Initial
implementation" line accordingly.
In `@Frends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.cs`:
- Around line 38-53: The test currently hardcodes sensitive values in the
Connection instance (variable connectionUsernamePassword) — specifically the
Username, Password and ApplicationCertificatePassword properties — so change the
test to load these from environment variables (use dotenv in the test setup and
read via Environment.GetEnvironmentVariable) and assign those variables to
connectionUsernamePassword.Username, connectionUsernamePassword.Password and
connectionUsernamePassword.ApplicationCertificatePassword; keep fallback or
assert they exist in setup to fail fast if the env vars are missing.
- Around line 142-144: The test currently only asserts the error message after
calling Opcua.Write; add an explicit assertion that the call failed by checking
the Success flag (e.g., assert result.Success is false) in the same test so the
failure contract is validated, then keep the existing Assert on
result.Error.Message to verify the reason; locate the test that calls
Opcua.Write and add an assertion against result.Success (or
Assert.IsFalse(result.Success)/Assert.That(result.Success, Is.False)) before or
alongside the existing message assertion.
In `@Frends.Opcua.Write/Frends.Opcua.Write.Tests/generate-certs.sh`:
- Line 115: The script currently writes nodesfile.json to a hardcoded path using
"cat > Volumes/nodesfile.json << 'EOF'", which ignores the configurable
OUTPUT_DIR; change that invocation to use the OUTPUT_DIR variable (e.g., "cat >
${OUTPUT_DIR}/nodesfile.json << 'EOF'") so the --output/OUTPUT_DIR option
controls where nodesfile.json is written; update any other hardcoded references
to Volumes for nodesfile.json to reference OUTPUT_DIR as well.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.cs`:
- Around line 33-39: The validation currently indexes each JToken (token[field])
assuming it's an object which throws for non-object items; inside the
ValidJsonArrayAttribute validation method (the loop over parsed and
requiredFields), first check that token.Type == JTokenType.Object (or token is
JObject) and if not return a ValidationResult indicating the offending
non-object entry, then only access token[field] to check for missing required
fields; apply the same clear ValidationResult message format used elsewhere so
validation returns an error instead of throwing.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Definitions/Connection.cs`:
- Around line 26-29: The Port property (and other numeric timeout properties in
the same class) lack range validation and can accept 0/negative values; add
DataAnnotations Range attributes to enforce valid values: annotate Port with
[Range(1, 65535)] and annotate each timeout-related int property with [Range(1,
int.MaxValue)] (or a sensible upper bound) and keep the existing default values;
also add the using for System.ComponentModel.DataAnnotations if missing so the
attributes compile.
- Around line 42-43: The AutoAcceptUntrustedCertificates property in the
Connection class currently defaults to true, which is insecure; change its
default to false and update the [DefaultValue] attribute to match so the
property and metadata reflect the secure default—locate the
AutoAcceptUntrustedCertificates property in class Connection and set its
initializer and DefaultValue to false.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Definitions/Error.cs`:
- Line 20: The public result type exposes an Exception via the AdditionalInfo
property on the Error class; change AdditionalInfo to a simple serializable type
(e.g., string or a small DTO) to avoid returning Exception objects. Update the
Error class (the AdditionalInfo property) to hold a flat payload such as string
AdditionalInfo or a custom ErrorDetail DTO (e.g., ErrorDetail { string Message;
string Type; string StackTrace? }) and adjust any code that sets AdditionalInfo
(constructors/factories in the same class or callers) to populate the new simple
fields instead of assigning Exception instances.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Definitions/Result.cs`:
- Line 19: The public property Nodes in the Result class is declared as dynamic;
replace it with a strongly typed collection that matches the documented node
result shape (e.g. List<NodeResult> or IReadOnlyList<NodeResult>) and add a new
NodeResult (or NodeWriteResult) DTO that contains the documented fields; update
the Result.Nodes type to that collection and adjust any
serialization/constructor/consumer code that reads/writes Nodes (methods
referencing Result.Nodes, serializers, and tests) to use the new NodeResult type
so tooling and compile-time checks can validate the contract.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Enums/InputType.cs`:
- Line 13: The enum member InputType.JSON should be renamed to InputType.Json to
follow C# naming rules for abbreviations; update the declaration in the
InputType enum and then update all usages and any serialization/parse logic that
reference the old JSON name (search for "InputType.JSON", string literals,
switch cases, and any JSON/enum mapping code) to use InputType.Json so the API
remains consistent and compilation succeeds.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.cs`:
- Line 163: The fallback error message incorrectly says "OPC UA node read
failed" even though this is in the write task; update the fallback string used
where statusCode is mapped (the switch/expression that returns $"OPC UA node
read failed with status: {statusCode}") to say "OPC UA node write failed with
status: {statusCode}" so the error references a write operation (adjust the
expression in Frends.Opcua.Write.cs where statusCode is formatted).
In `@Frends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.csproj`:
- Line 15: The <RepositoryUrl> element currently points to the Read project;
update the <RepositoryUrl> value so it references the Write project (change the
URL from .../Frends.Opcua.Read to .../Frends.Opcua.Write) in the project file so
tools and users are directed to the correct repository page; ensure the tag
remains
<RepositoryUrl>https://github.com/FrendsPlatform/Frends.Opcua/tree/main/Frends.Opcua.Write</RepositoryUrl>.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Helpers/OpcUaSession.cs`:
- Around line 24-30: The DisposeAsync method in class OpcUaSession should
guarantee Session.Dispose() runs even if Session.CloseAsync() throws: wrap the
CloseAsync call in a try/finally (or try/catch/finally) so that you await
Session.CloseAsync() only if Session.Connected but always call Session.Dispose()
in the finally block; reference the DisposeAsync method and the
Session.CloseAsync and Session.Dispose members when making the change.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Helpers/SessionFactory.cs`:
- Around line 182-184: The temporary RSA instance created with RSA.Create()
(variable privateKey) must be disposed deterministically; in SessionFactory.cs
wrap the RSA creation/import block in a using (or otherwise call Dispose) so you
import the PEM into privateKey, call cert.CopyWithPrivateKey(privateKey) to
produce the new certificate, and then return that new certificate after the RSA
has been disposed; reference RSA.Create(), ImportFromPem, privateKey, and
cert.CopyWithPrivateKey to locate and update the code.
In `@Frends.Opcua.Write/Frends.Opcua.Write/migration.json`:
- Line 3: The migration.json currently sets the migration target "Task" to
"Frends.Opcua.Read" which is incorrect for this project; update the "Task" value
in migration.json to "Frends.Opcua.Write" so the migration metadata applies to
the correct task identifier.
---
Nitpick comments:
In `@Frends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.cs`:
- Line 68: Remove the debug artifacts from the FunctionalTests class: delete the
commented-out hardcoded path fragment from the PrivateKeyPath assignment (the
commented Path.Combine line next to PrivateKeyPath = string.Empty) and remove
the diagnostic Console.WriteLine calls printed in the test (the console output
around lines 149–152) so the test contains no commented-out test paths or
transient diagnostic prints; keep the PrivateKeyPath set to string.Empty and
ensure no other references to the removed debug prints remain in the
FunctionalTests class.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.cs`:
- Line 3: The project relies on Newtonsoft.Json via transitive dependencies but
files like ValidJsonArrayAttribute.cs (class ValidJsonArrayAttribute) reference
Newtonsoft.Json.Linq directly; add an explicit PackageReference for
Newtonsoft.Json to the project that contains ValidJsonArrayAttribute (and any
other projects that directly use Newtonsoft.Json types) in its .csproj so the
build does not rely on transitive packages, then run dotnet restore / rebuild to
verify resolution.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Helpers/ErrorHandler.cs`:
- Around line 26-29: The ThrowIfCanceled method currently rethrows
OperationCanceledException using "throw exception;" which resets the stack
trace; update ThrowIfCanceled(Exception exception, bool throwCanceled = true) to
rethrow via ExceptionDispatchInfo.Capture(exception).Throw() (and ensure the
appropriate using for System.Runtime.ExceptionServices is added) so the original
stack trace is preserved when exception is an OperationCanceledException and
throwCanceled is true.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: dd96591c-483b-4e13-8f24-2a58ecf25cb0
📒 Files selected for processing (36)
.github/workflows/Write_release.yml.github/workflows/Write_test_on_main.yml.github/workflows/Write_test_on_push.ymlFrends.Opcua.Write/CHANGELOG.mdFrends.Opcua.Write/Frends.Opcua.Write.Tests/ErrorHandlerTest.csFrends.Opcua.Write/Frends.Opcua.Write.Tests/Frends.Opcua.Write.Tests.csprojFrends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.csFrends.Opcua.Write/Frends.Opcua.Write.Tests/GlobalSuppressions.csFrends.Opcua.Write/Frends.Opcua.Write.Tests/TestBase.csFrends.Opcua.Write/Frends.Opcua.Write.Tests/docker-compose.ymlFrends.Opcua.Write/Frends.Opcua.Write.Tests/generate-certs.shFrends.Opcua.Write/Frends.Opcua.Write.slnFrends.Opcua.Write/Frends.Opcua.Write/Attributes/RequiredIfAttribute.csFrends.Opcua.Write/Frends.Opcua.Write/Attributes/RequiredToExistIfAttribute.csFrends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Connection.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Error.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Input.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Options.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Result.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/WriteNode.csFrends.Opcua.Write/Frends.Opcua.Write/Enums/AuthenticationMode.csFrends.Opcua.Write/Frends.Opcua.Write/Enums/InputType.csFrends.Opcua.Write/Frends.Opcua.Write/Enums/OpcMessageSecurityMode.csFrends.Opcua.Write/Frends.Opcua.Write/Enums/OpcSecurityPolicy.csFrends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.csFrends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.csprojFrends.Opcua.Write/Frends.Opcua.Write/FrendsTaskMetadata.jsonFrends.Opcua.Write/Frends.Opcua.Write/GlobalSuppressions.csFrends.Opcua.Write/Frends.Opcua.Write/Helpers/ErrorHandler.csFrends.Opcua.Write/Frends.Opcua.Write/Helpers/OpcUaSession.csFrends.Opcua.Write/Frends.Opcua.Write/Helpers/SessionFactory.csFrends.Opcua.Write/Frends.Opcua.Write/Helpers/ValidationHandler.csFrends.Opcua.Write/Frends.Opcua.Write/migration.jsonFrends.Opcua.Write/README.mdREADME.md
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Frends.Opcua.Write/Frends.Opcua.Write.Tests/generate-certs.sh`:
- Line 115: The redirection target in generate-certs.sh uses an unquoted
variable (cat > $OUTPUT_DIR/nodesfile.json << 'EOF') which will break on paths
with spaces or glob characters; change the redirection to use a quoted expansion
for the output path (i.e. redirect to "$OUTPUT_DIR/nodesfile.json") so the shell
treats the whole path as a single token while preserving the here-doc and the
nodesfile.json filename.
In `@Frends.Opcua.Write/Frends.Opcua.Write/Definitions/Connection.cs`:
- Around line 103-104: ConnectionTimeout and SessionTimeout can overflow when
multiplied by 1000 in SessionFactory (used for sessionTimeout:
(uint)(connection.SessionTimeout * 1000), OperationTimeout =
connection.ConnectionTimeout * 1000, DefaultSessionTimeout =
connection.SessionTimeout * 1000); tighten the allowed range or clamp values
before millisecond conversion to prevent overflow: update the Range on
ConnectionTimeout and SessionTimeout to use a max of int.MaxValue/1000 (or a
safe constant like 2_147_483) and/or ensure the multiplication uses a safe clamp
(e.g., Math.Min(value, int.MaxValue / 1000)) and then cast to uint/long as
needed in SessionFactory to guarantee no overflow when multiplying by 1000.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: cceba95a-f87c-473d-bf34-cfe7dd9e8380
📒 Files selected for processing (11)
Frends.Opcua.Write/Frends.Opcua.Write.Tests/FunctionalTests.csFrends.Opcua.Write/Frends.Opcua.Write.Tests/generate-certs.shFrends.Opcua.Write/Frends.Opcua.Write/Attributes/ValidJsonArrayAttribute.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Connection.csFrends.Opcua.Write/Frends.Opcua.Write/Definitions/Input.csFrends.Opcua.Write/Frends.Opcua.Write/Enums/InputType.csFrends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.csFrends.Opcua.Write/Frends.Opcua.Write/Frends.Opcua.Write.csprojFrends.Opcua.Write/Frends.Opcua.Write/Helpers/OpcUaSession.csFrends.Opcua.Write/Frends.Opcua.Write/Helpers/SessionFactory.csFrends.Opcua.Write/Frends.Opcua.Write/migration.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please review my changes :)
Task Harmonization PR template
Review Checklist
1. Frends Task Project File
Frends.*/Frends.*/*.csproj<TargetFramework>net8.0</TargetFramework><Version>x.0.0</Version><Authors>Frends</Authors><PackageLicenseExpression>MIT</PackageLicenseExpression><GenerateDocumentationFile>true</GenerateDocumentationFile><Description><RepositoryUrl>https://github.com/FrendsPlatform/Frends.SYSTEM/tree/main/Frends.SYSTEM.ACTION</RepositoryUrl><Nullable>disable</Nullable>StyleCop.Analyzers v1.2.0-beta.556FrendsTaskAnalyzers v1.*<Content Include="migration.json" PackagePath="/" Pack="true"/><Content Include="../CHANGELOG.md" PackagePath="/" Pack="true"/><AdditionalFiles Include="FrendsTaskMetadata.json" PackagePath="/" Pack="true"/>2. Frends Task Test Project File
Frends.*/Frends.*.Tests/*.Tests.csproj<TargetFramework>net8.0</TargetFramework><IsPackable>false</IsPackable><Nullable>disable</Nullable>StyleCop.Analyzers v1.2.0-beta.5563. Additional Files
LICENSEfile per repository.gitignorefile per repository.idea/foldersFrends.*/README.mdFrends.*/CHANGELOG.mdFrends.*/Frends.*/FrendsTaskMetadata.jsonFrends.System.Action.System.ActionFrends.*/Frends.*/migration.jsonFrends.*/Frends.*/GlobalSuppressions.csFrends.*/Frends.*.Tests/GlobalSuppressions.cs4. Source Code
5. GitHub Actions Workflows
.github/workflows/*.yml*_release.ymlfeed_api_key: ${{ secrets.TASKS_FEED_API_KEY }}*_test_on_main.ymlbadge_service_api_key: ${{ secrets.BADGE_SERVICE_API_KEY }}*_test_on_push.ymlbadge_service_api_key: ${{ secrets.BADGE_SERVICE_API_KEY }}test_feed_api_key: ${{ secrets.TASKS_TEST_FEED_API_KEY }}GITHUB_TOKENworkdir: Frends.SYSTEM.ACTIONstrict_analyzers: truedotnet_version: 8.0.xprebuild_command: docker-compose up -d)Summary by CodeRabbit
New Features
Tests
Documentation
Chores