| So this may not actually be viable for a few reasons:
- Need to know when to execute whatever script the config section contributes - i.e., how do we know "Ok, run this snippet of code for the postBuild section after stages are done and before we leave the potential node block that stages are run in"? This is the biggie that I just can't figure out an answer to.
- Adding validation support via moving the methods in ModelValidator to the ModelASTElement extension in question is doable enough, but not ideal.
- Along the same lines, contributing to the JSON schema (or more accurately, generating the JSON schema dynamically from information provided by the various config sections) is probably doable but a bit ugly conceptually.
- ModelParser and JSONParser, on the other hand, would need complete rewrites. I'm not sure how we'd do that yet, but given the "when to execute" problem, I don't think it's worth it for me to invest much thought on this in particular yet.
|
