Skip to content

Add Java options for a correct generation#295

Open
disk91 wants to merge 13 commits intohelium:masterfrom
disk91:master
Open

Add Java options for a correct generation#295
disk91 wants to merge 13 commits intohelium:masterfrom
disk91:master

Conversation

@disk91
Copy link
Copy Markdown

@disk91 disk91 commented Mar 1, 2023

These options helps to generate Java classes for Config service properly

Copy link
Copy Markdown
Member

@madninja madninja left a comment

Choose a reason for hiding this comment

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

could you add a java CI build? That way we'll all know when stuff breaks

Copy link
Copy Markdown
Member

@madninja madninja left a comment

Choose a reason for hiding this comment

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

One comment and I'd still like to see a Java CI step to ensure this does not break in future builds

syntax = "proto3";

package helium;
option java_package = "xyz.nova.grpc";
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

can you rename this to com.helium.* please? This repo is in the foundation GitHub team

@disk91
Copy link
Copy Markdown
Author

disk91 commented Mar 20, 2023

Hello, It has been updated and the new files with header have been added


package helium;
option java_package = "com.helium.grpc";
option java_outer_classname = "regionparam";
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

regionparam and not RegionParam?

Copy link
Copy Markdown
Contributor

@jeffgrunewald jeffgrunewald Mar 28, 2023

Choose a reason for hiding this comment

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

or IotRegionParam for consistency with the region.proto outer class name?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Unfortunately, the generation is not working properly when you name it correctly. I do not remind the detail of the problem but it was not working with camelcase and upfront uppercase

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

how was the problem exhibited? At build time? If so, I would still like to see a CI step, just like we do for all other supported languages

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.

4 participants