Allows the developer to supply a custom directory that will be used as
the base of the protofiles.
```json
{
"invocations": [
{
"protoFiles": [
"file1.proto",
"file2.proto",
],
"visibility": "public",
"protoPath": "proto_repo_submodule/protos"
}
]
}
```
This is useful if you are storing protofiles inside a Git repo and
adding that as a submodule to other repos. Giving you a directory
structure like:
```
MySwiftApp/
- Sources
- MyAppTarget
- proto_repo_submodule
- protos
- file1.proto
- file2.proto
```
and any proto files will be importing other proto files relative to that
"protos" directory:
such as in **file1.proto**
```protobuf
import "file2.proto"
```
---------
Co-authored-by: Thomas Van Lenten <thomasvl@google.com>
Co-authored-by: Franz Busch <f.busch@apple.com>
### Motivation:
Swift 5.9 is no longer supported, we should bump the tools version
### Modifications:
* Bump the Swift tools version to Swift 5.10
* Remove unsupported versions from CI in build.yml
### Result:
Code reflects the expected support window.
# Motivation
We have seen a few issues with the SPM plugin over time that we could have caught with tests.
# Modification
This PR adds a new tested `PluginExamples` folder that contains a standalone package that exercises the plugin in various configuration. This does not only help in testing the various configurations but also is a good resource for people that want to adopt the plugin.
# Result
We now have tests in place making sure our plugin works
Mads Odgaard
Rick Newton-Rogers
Thomas Van Lenten
Jakub Skotnicki
Franz Busch