Skip to content

Conversation

@thompson-tomo
Copy link
Contributor

Closes #889

@devOpsHazelcast
Copy link
Contributor

PR closed by Hazelcast automation as no activity (>3 months). Please reopen with comments, if necessary. Thank you for using Hazelcast and your valuable contributions

@thompson-tomo
Copy link
Contributor Author

Reopen am awaiting feedback

@emreyigit
Copy link
Collaborator

emreyigit commented Aug 12, 2025

I can't accept this PR since it depends on a specific library.

@thompson-tomo
Copy link
Contributor Author

@emreyigit can you explain what you mean.

System.Memory is natively included in the framework as per https://apisof.net/catalog/fd22bb9adc9f2e905e80fbc8eb34b37b starting with net core 2.1 hence it is not required to be added an explicit dependency on the newer frameworks.

@emreyigit
Copy link
Collaborator

Sorry @thompson-tomo. Ignore my previous comment please. I just got your point. I need to verify the changes doesn't break anything. Currently, I have limited time but I've added to my to-do.

@emreyigit emreyigit reopened this Aug 12, 2025
@thompson-tomo
Copy link
Contributor Author

No worries, let me know if you have any questions.

@devOpsHazelcast
Copy link
Contributor

PR closed by Hazelcast automation as no activity (>3 months). Please reopen with comments, if necessary. Thank you for using Hazelcast and your valuable contributions

@thompson-tomo
Copy link
Contributor Author

@emreyigit could you re-open

@emreyigit emreyigit reopened this Nov 13, 2025
@codecov
Copy link

codecov bot commented Nov 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.45%. Comparing base (1613f8f) to head (500ec58).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #960      +/-   ##
==========================================
+ Coverage   81.43%   81.45%   +0.01%     
==========================================
  Files        1054     1054              
  Lines       25420    25420              
==========================================
+ Hits        20702    20707       +5     
+ Misses       4718     4713       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@emreyigit emreyigit left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution @thompson-tomo, I've left few comments. Also, could you resolve the conflict with master, please?

if (string.IsNullOrWhiteSpace(attributePath))
throw new ArgumentException("No attribute path can be null nor empty.", nameof(attributePaths));
#if NETFRAMEWORK
if (attributePath.Contains("[any]"))
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you revert this change since we target framework and behavior of methods is not same with core?

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 am looking at it but can you show me where we are targeting framework?


#pragma warning disable MA0048 // File name must match type name
#define INTERNAL_NULLABLE_ATTRIBUTES
#if NETSTANDARD2_0 || NETCOREAPP2_0 || NETCOREAPP2_1 || NETCOREAPP2_2 || NET45 || NET451 || NET452 || NET6 || NET461 || NET462 || NET47 || NET471 || NET472 || NET48
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here and other similar swaps between netstandart2.0 and net framework

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See above about these being controlling compilation and the current frameworks.

@thompson-tomo
Copy link
Contributor Author

@emreyigit conflict has been resolved. In regards to framework I am not sure I follow. The package is only compiled for net standard 2.0, 2.1 or net 6+. Net framework works as it will use the highest net standard compiled version compatible hence there is no need for the additional compilation symbols. In fact having them there is actually confusing as even though net47 is a condition in the if, the if is not satisfied given that net47 will use the version compiled for net standard 2.0 which is not a condition for the if.

Also I have no idea about the status of the github checks.

@emreyigit
Copy link
Collaborator

@thompson-tomo thank you for your contribution. Github checks doesn't trigger due to lack of permission but anyway, I triggered. I'm going to merge after tests passed.

@emreyigit emreyigit changed the title #889 optimise dependencies #889 optimise dependencies [API-2338] Nov 18, 2025
@emreyigit emreyigit added Type: Enhancement Code enhancement. Source: Community Originated from the Community. labels Nov 18, 2025
@emreyigit emreyigit added this to the 5.6.0 milestone Nov 18, 2025
@emreyigit emreyigit merged commit e29d565 into hazelcast:master Nov 18, 2025
20 checks passed
@thompson-tomo
Copy link
Contributor Author

Ahh ok @emreyigit no worries. I was just confused that it was showing as failed.

@thompson-tomo thompson-tomo deleted the chore/#889_OptimiseDependencies branch November 18, 2025 09:28
@emreyigit
Copy link
Collaborator

Merged. May I ask your use case if you don't mind? It's just out of curiosity since you mentioned that you aim to have a small build as much as possible.

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

Labels

Automation: PR auto closed Source: Community Originated from the Community. Type: Enhancement Code enhancement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Optimise dependencies to leverage framework

3 participants