Resolvable soft-validations about taxonworks HOT 7 CLOSED

This is increasingly being requested, and is becoming fairly high priority.

from taxonworks.

from taxonworks.

Are you now thinking about that approach as a replacement for the wirefame that was proposed?

from taxonworks.

from taxonworks.

Thinking quickly- I think we still need the form as we designed, but it's certainly not a bad step to do this first. We need to do the following:

• Extend the invocation pattern soft_validate(:other_soft_validation_method, set: :some_set, resolutions: ['route_name_only_no_path_or_url_postifx', ... 'other_path']) (prioritize the first path, but here recognize that tasks may ultimately overlap, so we might give users different views that both solve the problem- likely don't use this pattern too much, but at least make it possible)
• Extend SoftValidation (singular) with an accessor that stores an array of (see below) the resolution paths, set on initialization
• Add a helper method(s) that generated the fully qualified path to resolution, and optional other paths if there are more based on some click through event

Soft validation code is quite (very?) well tested, so we should be able to extend it quickly. Do you want me to tackle it, or do you want to take a look (and maybe make general improvements)?

from taxonworks.

With f7ec60a you can make a soft validation resolvable by including resolution_with: __method__ in soft_validations.add() (note that method is literally what you use). It feels a little crude, and not as automagic as it could be, but might be workable, and gives us the flexibility to user/not resolution with a particular soft validation instance. Need to further document what's going on.

from taxonworks.

Going to close this, the existing solution provides resolvable soft validations, albeit with some extra weight. We can open an new issue when we need specific changes.

from taxonworks.