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
Hello,I am testing the print function and noticed that it only appears to output results for the first holding/group. I can see from the example from the instructions that there is no json field for the group/holding name.
What is the expected behaviour when there are multiple holdings defined? Is it possible to have them separated by holdings? Short of creating separate yaml files, is there a hidden option which allows to display a holding which isn't the first one?
I'm pretty confident my yaml file is correct as the holdings are recognised in the tui and I can switch from one to the other.
Also, how can I get access to the new output added in this pull request? 1f83050
I have installed v4.8.0 but the output is still the same. It the syntax still ticket config=config.yaml print or is there a new option needed to see this information? (I tried "summary" but that did nothing)
The text was updated successfully, but these errors were encountered:
Hello,I am testing the print function and noticed that it only appears to output results for the first holding/group. I can see from the example from the instructions that there is no json field for the group/holding name.
What is the expected behaviour when there are multiple holdings defined? Is it possible to have them separated by holdings? Short of creating separate yaml files, is there a hidden option which allows to display a holding which isn't the first one?
I'm pretty confident my yaml file is correct as the holdings are recognised in the tui and I can switch from one to the other.
Also, how can I get access to the new output added in this pull request? 1f83050
I have installed v4.8.0 but the output is still the same. It the syntax still
ticket config=config.yaml print
or is there a new option needed to see this information? (I tried "summary" but that did nothing)The text was updated successfully, but these errors were encountered: