-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate allowing optional package
parameters when parsing Protobuf schema
#318
Comments
@dmarticus, to add some clarity, my problems with the
As for a real-world example, my original |
@a7emenov do you have an example protobuf file that I could work with that you'd like to be able to use with mu and skeuomorph? I'm planning on implementing this behavior this week and I'd love to have a file that you want to be able to convert to use as a test case |
@dmarticus, sure, thank you so much for a swift response. Example 1:
Example 2:
|
Thank you for sharing! These will be some great test cases for my implementation; I appreciate it! |
@a7emenov we should be releasing this change this week! Thanks for your help in providing the context around it and I hope you find the changes helpful :) |
@dmarticus, I can't properly express how much this helps! Much obliged for acting so swiftly, this basically allows to keep using |
@a7emenov my pleasure! It's great to have users who push the envelope of what we've made and identify gaps, so I appreciate you for that. The release went out today (https://gitter.im/47deg/mu?at=5f4d6fa5dfaaed4ef521757a), and I'll publish the changes to |
Per this discussion in gitter
It seems like at least one person would want us to allow for optional package generation within skeuomorph and mu. I'm not sure at this point how significant of an undertaking that work would be but I figured it's worth making a task to track it so we can triage at some point in the future
The text was updated successfully, but these errors were encountered: