You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is a comment for future redesign of the matlab diagnostics. there's something not right about how this was implemented if adding a new model to the diagnostics requires every .m file to have the case statement updated with the name of the model.
for example, the pinfo structure could define categories of models (e.g. 1d, 3d, etc), in addition to the model name. to add a new model that is similar to an existing one, you set the appropriate category string. then these files have a case statement on pinfo.category. as long as you're not adding a model that needs different code, you wouldn't have to change the .m files at all.
This discussion was converted from issue #319 on May 24, 2022 20:32.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
this is a comment for future redesign of the matlab diagnostics. there's something not right about how this was implemented if adding a new model to the diagnostics requires every .m file to have the case statement updated with the name of the model.
for example, the pinfo structure could define categories of models (e.g. 1d, 3d, etc), in addition to the model name. to add a new model that is similar to an existing one, you set the appropriate category string. then these files have a case statement on pinfo.category. as long as you're not adding a model that needs different code, you wouldn't have to change the .m files at all.
Originally posted by @nancycollins in #262 (comment)
Beta Was this translation helpful? Give feedback.
All reactions