Skip to content

Conversation

@adamegyed
Copy link
Contributor

Motivation

As discussed in the working group sync, the default validation PR #63, and other PR comments, we may want to avoid using the term "default" when discussing default validation. Specifically, default implies that there is one specific validation used across many execution functions, and that it will be selected automatically, which are not the case.

Proposed Solution

One possible rename is to convert it to the term "global". This gets rid of the downsides of the term "default". However, it may carry the connotation that a "global" validation function applies to all functions, but in reality, a function must opt in to this validation.

Putting up this PR to discuss the proposed name change. Personally I'm OK with either.

@adamegyed adamegyed requested a review from a team June 21, 2024 17:43
Copy link
Collaborator

@jaypaik jaypaik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Until we come up with a better name for this, I prefer this over default.

@adamegyed adamegyed force-pushed the adam/propose-rename-default-global branch from 384f946 to 2d599db Compare July 10, 2024 17:31
@adamegyed adamegyed merged commit 30596f8 into v0.8-develop Jul 10, 2024
@adamegyed adamegyed deleted the adam/propose-rename-default-global branch July 10, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants