Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed unused namespace creating conflict #33

Conversation

masesdevelopers
Copy link
Contributor

Description

Related Issue

fix #12

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 added the bug Something isn't working label Jun 3, 2024
@masesdevelopers masesdevelopers self-assigned this Jun 3, 2024
…eflector-classes-shall-be-changed-manually-9
@masesdevelopers masesdevelopers merged commit 5021883 into masesgroup:master Jun 3, 2024
2 checks passed
@masesdevelopers masesdevelopers deleted the 12-waiting-for-an-updated-version-of-jnetreflector-classes-shall-be-changed-manually-9 branch June 3, 2024 03:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Waiting for an updated version of JNetReflector classes shall be changed manually
1 participant