Comments (2)
Ignoring the package name when generating filenames was a very deliberate decision on my part.
I've many times in the past tried to use protoc with make
or Xcode build rules and found it very frustrating. Having the generator build a single output file in the current directory from a single input file makes it easy to do simple things with common build systems. (This is also why the plugin does not mangle filenames like the Obj-C generator does or build multiple output files for a single input like the Java generator does.)
Tools like Bazel with specialized knowledge of proto semantics may be necessary for complex cases, but are overkill for common cases where people have just one or two protos in a project.
I would not be opposed to having alternate mechanisms that can generate more structured output, but I'm reluctant to make simple cases complicated by default.
from swift-protobuf.
Re-reading, I now realize that the proposal was to use the input directory name when generating the output, not the input package name. The directory name is visible to build tools, so I could agree to that.
from swift-protobuf.
Related Issues (20)
- Revisit `_NameMap` in light of Swift 5 changing the default `String` encoding HOT 1
- 2 .proto has the same message names, which is why the project is not going to be built HOT 1
- Package Resolution Failed in Xcode 15.3 HOT 1
- Can I use SwiftProtobufPluginLibrary or SwiftProtobuf as a Protobuf-parser in Swift project? HOT 1
- The "thread" sanitizer testing is failing HOT 8
- The fuzz regression tests seem to have stopped working. HOT 2
- Need to Add a Privacy Manifest for Apple Validation store for sprint 2024 HOT 1
- Add a PrivacyInfo file HOT 1
- TextFormat seems like it might not be to spec for "inf", "infinity", or "nan" HOT 2
- PR approved back in July 2022 and changes still not included in a release HOT 7
- Unable to verify code signature when installing app to iOS from XCode HOT 4
- Primitive one-of type always passes nil as its argument for decoder HOT 8
- Serialization is not generated HOT 8
- Support for Protobuf Editions HOT 2
- Un-revert breaking changes before releasing v2
- Consider support for newer concepts like `BitwiseCopyable` HOT 1
- SwiftProtobuf.xcodeproj cannot be opened because it is missing its project.pbxproj file. HOT 4
- New `CodeGenerator` protocol should allow customising the `Google_Protobuf_Compiler_CodeGeneratorRequest` HOT 7
- SwiftProtobufPluginLibrary.FileDescriptor.proto is deprecated HOT 13
- xCode shell script doesn't run HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swift-protobuf.