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 don't know exactly what this looks like yet, but I have a ton of really large custom JSON output in my actions that are too complex to say response.should send_json(200, messages: [{.......}]). Really I don't care that the value looks exactly a specific way, I just want to ensure that there is a value from that key. So really I want something kind of like..
Thinking about this more... Maybe we can just do deep nested checks? For example, I want to know if the response has a key with a value that's a massive object, but I only need to verify that one of the key/values in that massive object exist...
This would then let me just do a quick few spot checks on an object instead of trying to worry about the exact time on created_at, or building out each object in a sub array and so on.
I don't know exactly what this looks like yet, but I have a ton of really large custom JSON output in my actions that are too complex to say
response.should send_json(200, messages: [{.......}])
. Really I don't care that the value looks exactly a specific way, I just want to ensure that there is a value from that key. So really I want something kind of like..or maybe comparing a type somehow?
definitely a half-baked idea 😂
lucky/src/lucky/request_expectations.cr
Line 12 in 8eef897
The text was updated successfully, but these errors were encountered: