You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose a single JTAF binary which consumes both individual JTAF programs. This is mainly to make the user journey simpler and build steps.
Usage
Users would compile a single binary and instantiate it with flags which activate a code path. For example, to generate the YANG XPath expressions:
./jtaf -processYang -config ./config.toml
Similarly, to process the provider:
./jtaf -processProvider -config ./config.toml
It would be simple to create a single JTAF binary and add flags to control internal flow. The result would be a single application instead of two separate binaries.
Let's discuss here. I'm happy to take this on if there is agreement. This would also act as a foundation for other work as we add features.
The text was updated successfully, but these errors were encountered:
I propose a single JTAF binary which consumes both individual JTAF programs. This is mainly to make the user journey simpler and build steps.
Usage
Users would compile a single binary and instantiate it with flags which activate a code path. For example, to generate the YANG XPath expressions:
Similarly, to process the provider:
It would be simple to create a single JTAF binary and add flags to control internal flow. The result would be a single application instead of two separate binaries.
Let's discuss here. I'm happy to take this on if there is agreement. This would also act as a foundation for other work as we add features.
The text was updated successfully, but these errors were encountered: