Name for the check field and process for teal_data object

[m7pr]

tHey, this poll is motivated by this feature request #182 and this PR #188

Currently you are able to create teal_data() object and pass datasets and the code during the creation. This means some datasets exist in teal_data@env but we have no guarantee that @code that hosts the code during the creation of the object actually creates datasets in teal_data@env.

We want to create a function that will review if the teal_data@code can recreate objects existing in teal_data@env. We need a name of the function that would do that. We also want to store an information if this check/review was performed in a separate teal_data field/slot. Name should also correspond to the process.

If you want to get biased, you can skim this thread #188 (comment)
I can not add any more items to the poll so if you see some combination that you prefer but does not exist, please write that in comments.

[chlebowa]

I would also take @valid + verify().

[kartikeyakirar]

If I had to choose from a list, I would select the @Valid field and the validate_code() function. It would be preferable to have longer names to increase clarity, unless there's a reason not to. The name should accurately reflect the purpose of checking whether teal_data@code can accurately recreate teal_data@env. With that in mind, here are some of suggestions (i tried using chatgpt to create more meaning full combinations)

@reproducibility_status + Function: check_reproducibility() (my 1st preference)
@code_validity + Function: validate_code() (my 2nd preference)
@verification_status + Function: verify_[data/env]_consistency()
@data_integrity + Function: assess_data_integrity()/ assess_code_validity()

some additional combination based on chatGPT

@consistency_check + Function: evaluate_consistency()
@code_reliability + Function: test_code_reliability()
@environment_validation + Function: confirm_env_setup()
@dataset_verification + Function: inspect_dataset_creation()
@recreation_status + Function: verify_recreation()
@integrity_check + Function: perform_integrity_test()
@reproducibility_assessment + Function: assess_reproducibility()
@execution_verification + Function: check_execution_accuracy()

[m7pr]

Thanks @kartikeyakirar those are great propositions. I only reckon the field/slot name should be one word to make it simple :)

[donyunardi]

I also like @valid and validate_code()

[donyunardi]

Find the better name for validate() function as it is already in shiny (to avoid masking)

@gogonzo already mentioned this so let's not use validate()

[lcd2yyz]

Suggest @valid_code and validate_code() as a clear paired usage =)