Open rob-buskens-sp opened 1 year ago
I started looking at another option... which was highlighting / adding things to the problems view (source not found, attribute not found, etc.). looks like that requires a language server implementation which ups the ante.
I also thought about completion, but, as you said, that would require a language server. We already implemented evaluation of transforms. We should be able to do something similar for validation.
Problem: Getting the sourceName name and/or attributeName wrong in account attribute transforms or the name attribute in identity attribute transforms. These errors can be sometimes hidden when used with other transforms such as first valid.
Either validate on save (or a command), that the info in the source attributes, identity attributes (scope creep: reference attribute.id) or have a command that you can insert them with, and then pick from the values the plugin already has from the tenant.
E.g. Source named "Employees - wonky2space", which has an schema attribute called "Hard2 Recall"
On save (or a validate command, check that the source exists, and that the attribute exists; or command insert: give pick list of available sources, then attributes (maybe even showing description (more scope creep)).