#4 Change to structures rather than needing glom

已關閉
david2 年之前創建 · 1 條評論

While my glom is kind of cool, it's also ugly (when I wrote it I was thinking this would be more popularly needed/used, but now that I understand how to deal with nested json and xml structures it's not ugly it's an extra dependency we can do without).

Currently as of 0e62ab3 I introduced a DeviceInfo structure (currently unused), which at least with the code I've seen so far is half the issue with our dependency to glom.

Todo:

  • Form MediaPlayer structure to handle the data we collect from the media-player info query. (See meow-bot's xml parsing out xml attributes)
  • Modify GetQuery to only return []byte received from the query (either device-info or media-player)
  • Implement usage of the new structures and update code to use them.
  • Removal of glom dependency will then be successful.
  • Profit!
While my glom is kind of cool, it's also ugly (when I wrote it I was thinking this would be more popularly needed/used, but now that I understand how to deal with nested json and xml structures it's not ugly it's an extra dependency we can do without). Currently as of 0e62ab3 I introduced a DeviceInfo structure (currently unused), which at least with the code I've seen so far is half the issue with our dependency to glom. Todo: - [x] Form MediaPlayer structure to handle the data we collect from the `media-player` info query. (See meow-bot's xml parsing out xml attributes) - [x] Modify GetQuery to only return []byte received from the query (either `device-info` or `media-player`) - [x] Implement usage of the new structures and update code to use them. - [x] Removal of glom dependency will then be successful. - [x] Profit!
david2 年之前 關閉

Closed in [79f2f89bef]

Closed in [79f2f89bef]
登入 才能加入這對話。
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容