One small issue I found: the keyword matching matches prefixes, so if there were two responses in the log for (say) <== KeywordOne {"id":1,"payload":{}} followed by <== KeywordOneHundred {"id":2,"payload":{}}, attempting to fetch <== KeywordOne fails as it attempts to parse Hundred {"id":2,"payload":{}} as a JSON string. Doesn't seem to affect the actual game logs for now.
One small issue I found: the keyword matching matches prefixes, so if there were two responses in the log for (say)
<== KeywordOne {"id":1,"payload":{}}
followed by<== KeywordOneHundred {"id":2,"payload":{}}
, attempting to fetch<== KeywordOne
fails as it attempts to parseHundred {"id":2,"payload":{}}
as a JSON string. Doesn't seem to affect the actual game logs for now.Originally posted by @pak21 in https://github.com/kelesi/mtga-utils/issues/19#issuecomment-558373540