Summary

Could you update your API terminology for id-whitelist and id-blacklist to be more inclusive? This could be a breaking change or you could immediately accept additional properties alongside the existing ones and phase them out at the next scheduled release.

I'm not sure whether users need to use these terms in order to use your API, but I see them in the changelog and in the code.

Motivation

The Code of Conduct says to use welcome and inclusive language and there's certainly more inclusive language that could be used for this part of the api. In addition, you're in the position of setting an example with the terminology that you choose to use. This post does a good job of detailing why the terms derive from prejudice: https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white

Additional Context

If id-allowlist and id-denylist don't fit exactly, alternative API properties could be excluded-ids, permitted-ids

Please note, this is my first issue request on a public API

Thank you for your understanding of the significance of this issue

Prior conversation on other repositories:

rails/rails#33677
FullHuman/purgecss#428
getsentry/sentry-javascript/issues/2640