Timeline for Validate JSON on server side
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2018 at 18:25 | history | edited | Laiv | CC BY-SA 3.0 |
deleted 7 characters in body
|
| Apr 12, 2018 at 17:54 | vote | accept | Mhd | ||
| Apr 11, 2018 at 19:58 | history | edited | Laiv | CC BY-SA 3.0 |
added 6 characters in body
|
| Apr 11, 2018 at 15:45 | history | edited | Laiv | CC BY-SA 3.0 |
Edited according @Christopher's comment
|
| Apr 11, 2018 at 15:44 | comment | added | Christopher | Still the best answer. If OP does not want to convert to C# objects then using JsonPath or Schemas is the next best thing (also great tool to have in your pocket). But unless it is noticeably impacting performance or scalability is a concern, they can probably maintain course. | |
| Apr 11, 2018 at 15:38 | comment | added | Laiv | @Christopher you are right. I focused only on the underlying question. | |
| Apr 11, 2018 at 14:53 | comment | added | Christopher | I think this addresses the nuanced question of "is this efficient", but for the actually question posed, I think the answer should include "Yes, this is a proper way to do validation - nothing is inherently wrong with the operation... But here are some other options if you want to improve performance and still maintain the current functionality". | |
| Apr 11, 2018 at 7:16 | history | edited | Laiv | CC BY-SA 3.0 |
spellcheck revision
|
| Apr 11, 2018 at 6:58 | history | edited | Laiv | CC BY-SA 3.0 |
added 98 characters in body
|
| Apr 11, 2018 at 6:44 | history | answered | Laiv | CC BY-SA 3.0 |