Skip to content
This repository has been archived by the owner on Aug 30, 2018. It is now read-only.

Suggestions for including proto files in installation #126

Closed
chekanov opened this issue Jun 27, 2018 · 3 comments
Closed

Suggestions for including proto files in installation #126

chekanov opened this issue Jun 27, 2018 · 3 comments

Comments

@chekanov
Copy link
Contributor

We need to include "model" mc.proto and other template files inside created PROIO files.
Therefore, I would suggested to copy the directory "model" to the installation location. Then one can link such files using the path $PROIO/model/mc.proto (as an example) during file creation of files.

There should be also a mechanism to store such files (and log files) inside PROIO

best, Sergei

@decibelcooper decibelcooper changed the title suggestions Suggestions for including proto files in installation Jun 27, 2018
@decibelcooper
Copy link
Owner

Hi Sergei (@chekanov), thanks! My thought is that File Descriptor protos are included in generated code, so in a sense these files are already being installed. There is also significant overlap here with #20. If we satisfy #20 and add the ability to dynamically deserialize unknown messages using the stored File Descriptor protos, does this satisfy your requirements?

@chekanov
Copy link
Contributor Author

Hi, David

Yes, this should work if this can be used for reading files with unknown data model.

@decibelcooper
Copy link
Owner

Hi Sergei (@chekanov),

Indeed this is the plan. I will close this issue in favor of #20, since this should be seen before closing that issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants