-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
How are we supposed to capture things like (from https://github.com/LEMS/LEMS/blob/master/examples/example1.xml)
```
```
in the schema???
-
Name spaces need to adjust automatically in xslt `.xsl` files, like `.govready/xml/scaninfo.xsl` depending on names space of schema used to scan.
`.govready/xml/scaninfo.xsl` and `.govready/xml/scani…
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …
-
```
What steps will reproduce the problem?
1. Define an enum item in the proto the Google naming guidelines, e.g.
"RESOURCE_LIBRARY",
2. The enum item gets generated as "RESOURCELIBRARY" in the enum …