Skip to content

Conversation

@masesdevelopers
Copy link
Contributor

Description

Related Issue

fix #38

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

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

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@masesdevelopers masesdevelopers self-assigned this Jul 27, 2025
@masesdevelopers masesdevelopers added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 27, 2025
masesdevelopers and others added 7 commits July 28, 2025 15:08
…ease-2-6-0' into 38-jnet-shall-be-always-aligned-to-latest-jcobridge-release-2-6-0-update-documentation
…jcobridge-release-2-6-0-update-documentation
* Update generated classes after commit 678c9d3

* Code fix

---------

Co-authored-by: masesdevelopers <94312179+masesdevelopers@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JNet shall be always aligned to latest JCOBridge release

1 participant