jwickberg
commented
2 years ago There is no version field that Paratext maintains as project text is changed - Mercurial history or saving a checksum during your update process would be the only options I can think of.
Currently, history is not available through the plugin interface, so that would need to be a change to the interface. I'm not sure when work like that would be scheduled.
On Thu, Nov 10, 2022 at 9:09 AM GeoDirk @.***> wrote:
As part of our plugin, we are consuming the project text, parsing it, tokenizing it, and storing it into a database. But that only gets us a current snapshot of the text. What would help us is to know that on this date, we got version x.x.x.0 of the text. Tomorrow, we have now have version x.x.x.1 of the text. Do you have anything like that in Paratext which could be exposed by the API?
Alternatively, there probably is something within the Mercurial file system that we could read in. But that sounds like a way more painful route to have to go.
— Reply to this email directly, view it on GitHub https://github.com/ubsicap/paratext_demo_plugins/issues/21, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANSZJUS474N7UBFTGSCYKDWHT6X3ANCNFSM6AAAAAAR4TBRL4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
GeoDirk
As part of our plugin, we are consuming the project text, parsing it, tokenizing it, and storing it into a database. But that only gets us a current snapshot of the text. What would help us is to know that on this date, we got version x.x.x.0 of the text. Tomorrow, we have now have version x.x.x.1 of the text. Do you have anything like that in Paratext which could be exposed by the API?
Alternatively, there probably is something within the Mercurial file system that we could read in. But that sounds like a way more painful route to have to go.