Skip to content

Conversation

@ebariaux
Copy link
Contributor

No description provided.

@ebariaux ebariaux requested a review from Miggets7 May 28, 2025 08:54
Copy link
Contributor

@Miggets7 Miggets7 left a comment

Choose a reason for hiding this comment

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

Some minor things to be discussed.

Overall it looks very well structured!

Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be committed? I would say it wil be generated locally when working on the project?

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 tried a bit but couldn't get the gradle build to work.
I will give it another go.

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 created #43 to handle this issue.

@ebariaux
Copy link
Contributor Author

Thanks, I'll take a look at those, maybe we can have a quick call next week

Copy link
Contributor

@Miggets7 Miggets7 left a comment

Choose a reason for hiding this comment

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

Just a few questions, overall it looks very good!

Copy link
Contributor

Choose a reason for hiding this comment

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

Not my expertise, but is it something we cannot test?

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 wanted to implement test, as I have on iOS side, but with my limited understanding of Kotlin and co-routines and I did not manage to come up with code that could handle the async nature of the provider.
Created #44 to address this later but I'd like to merge this PR even without tests for now.

Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't the proto file be present somewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In the end, I managed to generate this class from the protobuf spec, latest commit performs that and basically fixes #43

@ebariaux ebariaux requested a review from Miggets7 January 6, 2026 10:16
Copy link
Contributor

@Miggets7 Miggets7 left a comment

Choose a reason for hiding this comment

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

Nice work!

If I can be of any help with the testing part of the protobuf stuff, let me know,

@ebariaux ebariaux merged commit 4310a46 into main Jan 7, 2026
1 of 2 checks passed
@ebariaux ebariaux deleted the feature/ESPProvisionProvider branch January 7, 2026 08:59
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.

3 participants