Page MenuHomePhabricator

[lib] Use tUserID in entry-validators.js pt.1
ClosedPublic

Authored by inka on May 9 2024, 4:03 AM.
Tags
None
Referenced Files
F3535937: D11961.diff
Wed, Dec 25, 5:02 PM
Unknown Object (File)
Oct 26 2024, 5:14 PM
Unknown Object (File)
Oct 26 2024, 1:01 AM
Unknown Object (File)
Oct 11 2024, 5:07 PM
Unknown Object (File)
Oct 11 2024, 5:07 PM
Unknown Object (File)
Oct 11 2024, 5:07 PM
Unknown Object (File)
Oct 11 2024, 5:06 PM
Unknown Object (File)
Sep 28 2024, 4:20 PM
Subscribers

Details

Summary

issue: ENG-7819

The approach I took is to go through all validators files in lib/types/validators and for each file, for each validator, recursively update all validators it uses

Test Plan

flow
Tested that fetch_entries endpoint which uses fetchEntryInfosResponseValidator works correctly and doesn't throw errors

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

inka requested review of this revision.May 9 2024, 4:19 AM

It might be a good idea to have a sanity check in a test plan to verify if the responses are validated correctly (if sending and receiving responses from keyserver work, for a couple of endpoints).

This revision is now accepted and ready to land.May 9 2024, 7:59 AM

It might be a good idea to have a sanity check in a test plan to verify if the responses are validated correctly (if sending and receiving responses from keyserver work, for a couple of endpoints).

Amended the test plan, going to check some other responders and amend test plans in proper diffs