nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsef7u3d what are you getting at? I'm unsure how you're saying to use this for qa. Like I get it for apps to use, but I don't understand what you're saying about using this when testing clients.
Not sure, I was just primarily responding to nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcprpmhxue69uhhyetvv9ujuen0w4h8gctfdchxvmf0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcprpmhxue69uhkzapwdehhxarjwahhy6mn9e3k7mf0qyvhwumn8ghj7er9wfnkjemf9ehx7um5wgcjucm0d5hszythwden5te0xy6rqtnxxaazu6t09uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9uq3wamnwvaz7tmzw33ju6mvv4hxgct6w5hxxmmd9uq36amnwvaz7tmgdyhx67tkda5kxet0w4e8xar0wfujummjvuhszgrhwden5te0vf5hgcm0d9hx6ctcd9kkzmrfwd68xtn0dekxjmn99uq3qamnwvaz7tm99ehx7uewd3hkctcpr9mhxue69uhkwun0w4c8xtnxd9shg6npvchxxmmd9uq3jamnwvaz7tmvd9nksarwd9hxwun9d3shjtnrdakj7qgmwaehxw309ankcetpwdhkuct5daezuer9wchhyetvv9uszrmhwden5te0gphx7uewd3hkctcpr9mhxue69uhks6ewwp6hyurvv4ex2mrp0yhxxmmd9uq3wamnwvaz7tmpw3kxzuewdehhxarj9ekxzmny9uq3vamnwvaz7tmgd9ehgtnwdaehgu3wd3skuep0qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3ctsk94x since he linked to the nostrability repo that hasn't been updated in almost 6 months. Wanted to clarify.
If Client A puiblishes a NIP-22 events without a root event tag, then Client B (and perhaps event Client A) won't be able to find it. Schemas can catch this error either in production or in a CI/CD pipeline. It can also detect these issues by fuzz testing events.
I would personally consider that QA, but maybe not?
Discussion
No replies yet.