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

Usage of Equatable package in GBFeature class #46

Open
OnlyTarg opened this issue Jul 22, 2023 · 1 comment
Open

Usage of Equatable package in GBFeature class #46

OnlyTarg opened this issue Jul 22, 2023 · 1 comment

Comments

@OnlyTarg
Copy link

Hey!
I would like to propose an enhancement for the growbook package that would make it even more convenient to use.

I suggest adding the usage of the equatable package to the GBFeature class to enable object comparison during the refresh of all features. This will allow users to easily determine if any changes occurred in the GBFeature without the need for additional checks at the user interface level.

Equatable is a library that simplifies object comparison based on their fields and automatically generates equals and hashCode methods. By adding Equatable to GBFeature, users can efficiently identify data changes during the refresh and take appropriate actions without unnecessary checks.

I believe that this enhancement will make growbooksdk even more appealing to developers and help save time by reducing the need for writing additional code to check for changes.

Thank you for considering my suggestion! I am available to provide any further information or answer any questions if needed.

@DK070202
Copy link
Contributor

Before we move forward, we'd like to gain a better understanding of how you are using refresh functionality. Could you provide an example or scenario where the refresh functionality is employed within the context of the GBFeature class? This would help us visualize how the Equatable enhancement would fit into the existing workflow and provide a clearer picture of its benefits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants