Confirm desired behavior and parameterization for when an existing value is specified in project card but doesn't match.

[e-lo]

Desired outcome: have a mechanism for a user be able to upgrade a warning to an error in the main wrangler API or configuration options.

Right now (in v1 RC)

• project cards can specify an existing value
• when they are applied using links.edit.edit_link_properties() you can set existing_value_conflict_error parameter:
  • if True, will trigger an LinkChangeError if the existing specified value in the project card doesn't match the value in links_df OR doesn't exist. Otherwise, will only trigger a warning. Defaults to False.
  • The issue is the way that it is currently triggered to True - or rather there isn't currently a way within the main API

Options

(not mutually exclusive)

In ascending order of complexity to implement:

1. Add as a parameter in params.py which would set the default behavior.
2. Add as a scenario configuration parameter which would then change how a scenario behaved.
3. Add as a parameter that can be set within a ProjectCard at a project level.

Recommendation

My (@e-lo ) recommendation is to implement 1 and if there is a use case for it, 2 but hold off on 3 because it would be more invasive and subject to fiddling and a lot of other cascading decisions.

Thoughts: @lmz @i-am-sijia @yueshuaing @DavidOry @RachelWikenMC ?

[e-lo]

Confirmed 1 and 2 are ok for v1 with @lmz and that project-card level functionality could be improvised by commenting out existing in project card.