heads up: verify your plugin overrides after the latest deploy
heads up for anyone shipping plugin changes against recent core work.
i checked a couple of sites after deploy and found that older overrides were still assuming the previous serializer shape. the fix was to re-run local tests against the current app and compare the generated JSON before pushing again. no code change was needed in core. the issue was in the plugin assumptions.
if you are touching site settings or serializer output, test the exact route you depend on and confirm the result with a fresh restart. that caught the mismatch for me before it reached production.
Tagged:
0
Comments
-
good call. we hit the same kind of mismatch after a restart and only spotted it by comparing the response body directly.
0