Yusuf Aran

feat(extend): allow adding of custom validators globally (#1077)

2

## Description Everything is already described in https://github.com/express-validator/express-validator/issues/1077. This PR is my suggested implementation for the validators part. I didn't implement it for sanitizers so far. ## To-do list -...

Allow simple extension of custom validators/sanitizers for better readability and reusability

3

## Is your feature request related to a problem? Please describe. When I add a custom validator, which I need to reuse, I usually create a function like this: ```js...

# Bug or Feature? Bug (might relate to #127) # Steps to reproduce 1. Add a custom DataEditor using `dataEditor` prop 1. Call `onCommit` of custom DataEditor before unmounting (using...

How to skip resolvers if fields are already there?

2

I'm using `nexus` with `prisma` and was mainly orienting myself on [this guide](https://nexusjs.org/docs/plugins/prisma/removing-the-nexus-plugin-prisma) to get things done more quickly. I will use the same example as [1:n relation section](https://nexusjs.org/docs/plugins/prisma/removing-the-nexus-plugin-prisma#1-n-relations) to...

Docs about scaling?

2

I couldn't find any docs related to scalability of bazel-remote, so I'm trying to get some Infos here. Generally, is it possible to scale bazel-remote horizontally? Lets say you start...

Field hook `afterChange` arg `previousValue` is only set correctly for fields in root of collection

3

### Link to reproduction https://github.com/ysfaran/payload/tree/reproduction-after-change-bug ### Describe the Bug When you create an `afterChange` hook for any nested field type like `type: 'group'` the hook will set the value for...

fix: sets previousValue for afterChange hook in nested fields correctly

5

Fixes: #4643 ## Description - [x] I have read and understand the [CONTRIBUTING.md](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md) document in this repository. ## Type of change - [ ] Chore (non-breaking change which does not...

## Issues While starting to work with CTRF and `playwright-ctrf-json-reporter` I noticed some ways to improve the errors. Resolving mentioned issues below would generally help to debug errors more easily....