Community
Participate
Working Groups
Actually the validating of the GMF-T input artifacts is process suitable for rather advanced users. There following general problems recognized: - validation messages are sometimes cryptic and normally don't contains a hints to solving the issues. - some correctly validated models still produce the problems at the codegen stage. - some of the reported validation problems are outdated and don't lead to any problems in the modern generated code. - it is impossible for toolsmith to accept some of the validation problems he know how to deal with and suppress them. In Kepler we should address this issues: - check and ensure the currency of the validation constraints - ensure better, clearer messages, possibly providing links to (external?) documentation about the possible consequences of the particular warning. - allow suppressing / unsuppressing of the triggered warnings - provide quick fixes (for some of the problems)
