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

chore: do not expose the artefact for open feature sdk #107

Closed
wants to merge 1 commit into from

Conversation

vahidlazio
Copy link
Contributor

No description provided.

Signed-off-by: vahid torkaman <vahidt@spotify.com>
@vahidlazio vahidlazio changed the title chore: use the maven artefact for open feature sdk chore: do not expose the artefact for open feature sdk Dec 15, 2023
@nicklasl
Copy link
Member

What do we/or the consumers of this SDK gain from this change?

@vahidlazio
Copy link
Contributor Author

@nicklasl ideally the consumers have one kotlin sdk and they can switch to different providers or have multiple providers, if the providers expose their own sdk this will be problematic in the future.

@nicklasl
Copy link
Member

@nicklasl ideally the consumers have one kotlin sdk and they can switch to different providers or have multiple providers, if the providers expose their own sdk this will be problematic in the future.

OK, I can get on board that. But we would need to update the README.md so it makes sense + keep that up to date with any SDK bumps we do.

@nicklasl nicklasl closed this Jul 2, 2024
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

Successfully merging this pull request may close these issues.

2 participants