the xml reader with its tests. #76
Conversation
…e repo, but it stops working due to my ssh key expiring, which made me then realise its not even part of our repos anymore (head shake) so putting them here until i figure out what the right place is.
…is works. we need to find a better way to fix the enviromental variable
…ent repos.this time the master brnach on telescope config data doesnt exist. its called main. likely a change from long ago. when peeps wanted to move away from master and slave inconitations.
|
this branch, when used in conjunction with: contains the basics for a optical interface. it contains a second database that builds a store based off data objects inside pst-lib. It also provides a rest interface for different elements from the optical telescope.
it also includes the xml reader for the xml files describing the telescope ui requirements. This includes code that removes some of the more offending issues with xml entries, which breaks the UI code hard. such as select boxes with no elements. |
|
oh. it also includes fixes to the github actions to utilise same name branches from dependent repos. a typical process for multi repo works. That stuff could be extracted as its own pr if you truly want. |
|
being shut down in favor of the all encompassing pr #86 |
this draft pr is holding point for all the xml reader work on the optical telescopes.
the xml reader itself is working. it no longer absorbs everything either. If the xml has commented out bits at the top level, the reader will respect that and not absorb the data associated with the commented out instruments. It will produce a mass of warnings about these issues. which we could clean up if we felt we had the time.
next is to tie it into the api and databases.