Right now, the plugin does validation in the linting/formatting sense - making sure that values that are supposed to be domains or are in the format of a domain, that TAG-IDs are 16 character hashes, that sort of thing. There are some external checks that could be done, such as ensuring a given exchange domain is a valid exchange and matches the TAG-ID supplied.
I don't know that this should ever be done directly in the plugin because it could be costly both in terms of user-perceived performance (slow external checks, finicky setups) and maintenance (constant changes that aren't reasonable to ship in a plugin's code). This issue is to track conversation and document awareness of these possibilities, even if they don't work out as plugin features.
Right now, the plugin does validation in the linting/formatting sense - making sure that values that are supposed to be domains or are in the format of a domain, that TAG-IDs are 16 character hashes, that sort of thing. There are some external checks that could be done, such as ensuring a given exchange domain is a valid exchange and matches the TAG-ID supplied.
I don't know that this should ever be done directly in the plugin because it could be costly both in terms of user-perceived performance (slow external checks, finicky setups) and maintenance (constant changes that aren't reasonable to ship in a plugin's code). This issue is to track conversation and document awareness of these possibilities, even if they don't work out as plugin features.