Review 11.10#11141
Conversation
| - We introduced a new Maia MCP Client Settings editor to make configuring and managing MCP Client Settings easier. | ||
| - Maia's capabilities can now be exposed as an MCP server, which you can enable in Maia preferences. This allows external agentic coding tools like Claude Code or Copilot to make modifications to your Mendix app, with changes reflected directly in Studio Pro. | ||
| - Maia can now fetch and interpret static web content such as external documentation, JSON specifications, and other publicly available documents. Note that it does not support content requiring authentication, dynamic web pages, or non-text formats. | ||
| - Maia can organize documents (excluding pages) into folders, following your existing folder structure, or using standard Mendix best practices. |
There was a problem hiding this comment.
Funny, because I think if the text was "follow your existing folder structure" it might have kept the Oxford series comma.
Might be worth putting "Maia can organize documents (excluding pages) into folders, follow your existing folder structure, or use standard Mendix best practices." into Claude and see if it correctly keeps the Oxford series comma in, thus following our style guide more correctly.
There was a problem hiding this comment.
But this changes the meaning of a sentence or do you mean to just use it for testing purposes?
| - We added the optional `selectedElementId` in the select methods of the element selector. If passed in, it will highlight the node with the corresponding id in the tree. | ||
| - We added the `http.nonProxyHosts` runtime configuration setting to specify hosts for which the runtime should not use a proxy. | ||
| - We added the ability to revert a commit from the history pane. You can now right-click a commit and select 'Revert Commit' to reverse the changes introduced by that specific commit. | ||
| - We introduced Update Assistant (beta) as a bottom panel in Studio Pro, where you can check Java action deprecations in your app. |
There was a problem hiding this comment.
Is lowercasing it correct? Or is beta in the doc title and thus require upper casing?
There was a problem hiding this comment.
Only if the capital letter is used in the UI (sometimes they add "Beta" to the name in the UI).
| - We upgraded to React 19.2 and React Native 0.83, bringing the latest performance improvements and features from both ecosystems. These updates provide enhanced rendering performance, improved native module integration, and a more modern foundation for building your low-code applications. | ||
| - We improved how Studio Pro stores the configuration microflow and the headers microflow in consumed OData services. These used to be stored in the same field. Now they are stored in two separate fields. When you switch from using a headers microflow to using a configuration microflow, Studio Pro will ask if you want to clear the headers microflow and vice versa. | ||
| - We upgraded to React 19.2 and React Native 0.83, bringing the latest performance improvements and features from both ecosystems. These updates provide enhanced rendering performance, improved native module integration, and a more modern foundation for building your apps. | ||
| - We improved how Studio Pro stores the configuration microflow and the headers microflow in consumed OData services. These microflows are now stored in two separate fields instead of the same field. When you switch from using a headers microflow to using a configuration microflow, Studio Pro asks whether you want to clear the headers microflow and vice versa. |
There was a problem hiding this comment.
This whether replacement for if might not be so good. Whether usually is followed by "or not" or "if", and I don't think the resulting sentence feels complete.
But this RN is badly written mostly due to the incredibly hard to parse "vice versa", so I sympathize with Claude doing its best.
The best version of this sentence is probably something like
"When you switch from using a headers microflow to a configuration microflow, Studio Pro will ask if you want to clear the headers microflow. Studio Pro will do the same check if you switch from a configuration microflow to a headers microflow."
There was a problem hiding this comment.
Implemented
| - Java action tracing span names now include the Java action name. | ||
| - We clarified the error message when upgrading solutions with files that have paths that are too long. | ||
| - We replaced the custom error screen in App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to support. | ||
| - Modernized console table now supports multi-selection via the context menu flow, allowing copying message and stack traces for multiple selected log lines. |
There was a problem hiding this comment.
I kind of think if it defaults to upper-casing Console here, it should also give it bolding (in keeping with the idea the user can see it in the UI).
Because console on its own doesn't sound like a private Mendix product, and named products are pretty much the only nouns we upper case in RNs without bolding them.
There was a problem hiding this comment.
I have reverted it to lower-casing.
| - We clarified the error message when upgrading solutions with files that have paths that are too long. | ||
| - We replaced the custom error screen in App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to support. | ||
| - Modernized console table now supports multi-selection via the context menu flow, allowing copying message and stack traces for multiple selected log lines. | ||
| - The `app-bundler` file in the project directory has been removed and replaced by a property in the model. The bundler selection (Rspack or Rollup) is now stored as part of the project settings instead of a file. |
There was a problem hiding this comment.
"project directory" is untouched but "project settings" is changed to "app" settings.
I think we need to validate what these things are called in product and set up Claude rules accordingly.
There was a problem hiding this comment.
Project directory is a file directory and app settings are in SP itself, I believe. I will change the formatting to make it more clear.
| - We replaced the custom error screen in App Explorer with a unified global error screen that provides a consistent experience and includes a refresh button and a direct link to support. | ||
| - Modernized console table now supports multi-selection via the context menu flow, allowing copying message and stack traces for multiple selected log lines. | ||
| - The `app-bundler` file in the project directory has been removed and replaced by a property in the model. The bundler selection (Rspack or Rollup) is now stored as part of the project settings instead of a file. | ||
| - We expanded the consistency checker to detect more page URL conflicts, so ambiguous navigation patterns are caught during design time rather than discovered at runtime. For example, `product/123` now correctly reports a conflict with `product/{Product/Id}`. For another example, `overview` and `over{view}` now reports a conflict. |
There was a problem hiding this comment.
Bad change, but I see why it tried it.
I recommend "For another example, the combination of overview and over{view} now reports a conflict."
Reports should have an S because combination is a singular noun. The way this was written previously was less clear.
There was a problem hiding this comment.
Implemented
| - We fixed an issue in published REST services in Studio Pro. Studio Pro would use the same field for (internal) documentation and public documentation (used in OpenAPI documents). Now these are two separate fields. | ||
| - We fixed an issue in modernized console panel where new logs appeared at the bottom of the table instead of the top when sorted in descending order. | ||
| - We fixed an issue where native macOS context menus could appear instead of the intended Studio Pro context menus. | ||
| - We fixed an issue in the modernized Runtime Console where the restart and stop buttons stopped working after the first restart. |
There was a problem hiding this comment.
Correct change, looks good.
Made me wonder though -- do we have logic for Claude to put in Keycap styling code if a RN is written like "Now you will enjoy improved functionality when pressing the Ctrl + V." ?
That would be very useful.
There was a problem hiding this comment.
Yes, we have that for Claude.
ConnorLand
left a comment
ConnorLand
left a comment
There was a problem hiding this comment.
I left my feedback and was largely pretty chuffed with the changes. Good tool!
Please let me know if there are any tasks you want me to take up persuant from these comments.
|
Hi @ConnorLand , thank you for your review, good points! I have implemented the comments, could you please take another look? |
2 participants
No description provided.