Review 11.10#11141
Open
MariaShaposhnikova wants to merge 2 commits intodevelopmentfrom
Open
Conversation
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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.
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
There was a problem hiding this comment.
Is lowercasing it correct? Or is beta in the doc title and thus require upper casing?
ConnorLand
reviewed
May 5, 2026
| - 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. | ||
| - We implemented a new function `DATEPARSE` in OQL. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateparse-function). | ||
| - We added support for the interrupting behavior on the workflow notification event sub-process **Start** event. When configured as interrupting, the event sub-process interrupts the parent workflow, terminating all active execution paths within the global scope, including activities in the main process and any nested sub-processes, before initiating the event sub-process flow. |
Collaborator
There was a problem hiding this comment.
This is good. We could try and steer Claude towards using parentheses for asides instead of commas (if that's more to our taste and keeps text clearer, in our opinion), but besides that I have no notes.
ConnorLand
reviewed
May 5, 2026
| - We implemented a new function `DATEPARSE` in OQL. For more information, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateparse-function). | ||
| - We added support for the interrupting behavior on the workflow notification event sub-process **Start** event. When configured as interrupting, the event sub-process interrupts the parent workflow, terminating all active execution paths within the global scope, including activities in the main process and any nested sub-processes, before initiating the event sub-process flow. | ||
| - We added a **Show** button in the element selector. Clicking it opens the selected element. | ||
| - We added the optional `selectedElementId` in the select methods of the element selector. When passed in, it highlights the node with the corresponding ID in the tree. |
Collaborator
There was a problem hiding this comment.
Good catching of if/should language
ConnorLand
reviewed
May 5, 2026
| - We added a new runtime setting `FileStorage.S3.DisableChunkedEncoding` to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789) | ||
| - We added a new Java API to create spans for tracing. The API is accessible via `com.mendix.core.Core.tracing()`. | ||
| - The Mendix runtime now responds to Cross-Origin Resource Sharing (CORS) preflight (`OPTIONS`) requests for client-facing endpoints. The responses include the custom headers configured in the runtime settings, allowing you to set up CORS for your application. | ||
| - The Mendix Runtime now responds to Cross-Origin Resource Sharing (CORS) preflight (`OPTIONS`) requests for client-facing endpoints. The responses include the custom headers configured in the runtime settings, allowing you to set up CORS for your app. |
ConnorLand
reviewed
May 5, 2026
| * If the project directory has been excluded from Windows Defender Antivirus. | ||
| - We fixed an issue where OQL‑based view entities could use an outdated ID column alias, leading to mismatches with Domain Model association names. A new App conversion step now detects these mismatches when opening the App and updates the column alias in OQL accordingly. | ||
| - We fixed an issue where copying a ViewEntity together with its associated Entity failed to include the connecting association. This association is now correctly copied whenever both elements are selected. Additionally, copying and pasting a ViewEntity now duplicates any linked in‑module or cross‑module Associations, assigning them new names and automatically updating their OQL references. | ||
| - We introduced a stricter requirements check on the server synchronization APIs for offline apps. This prevents entities from synchronizing changes when they are configured with the synchronization modes Online, Nothing, or Never. To allow older offline clients that have an All Objects or By XPath synchronization mode to still synchronize while the new app version has the entity configured with an Online, Nothing, or Never synchronization mode, we added a **Compatibility mode** checkbox. |
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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."
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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.
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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.
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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.
ConnorLand
reviewed
May 5, 2026
| - 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. |
Collaborator
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.
ConnorLand
approved these changes
May 5, 2026
Collaborator
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.