New String behavior toggle #10687
Open
New String behavior toggle #10687
+13
−1
Conversation
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
…the toggle in the upgrade guide.
Collaborator
|
@exec-astraea Can this be merged after review, as the release occurred this afternoon? |
Contributor
Author
|
@quinntracy yes. But this will also need an RnD review from @Robinfr. |
Collaborator
|
@exec-astraea Got it. Once @Robinfr approves, I'll take a look. |
Robinfr
suggested changes
Feb 2, 2026
| We understand that this change might cause unexpected changes in existing applications migrated from older versions of Mendix. | ||
|
|
||
| We recommend carefully analyzing all expressions that are comparing strings against `''` or `empty` and doing extensive testing after the migration. | ||
| In Mendix 11.6.3 we have introduced [an option](https://docs.mendix.com/refguide/app-settings/#new-sting-behavior) to toggle between the old and the new client-side String attribute behaviors. Projects migrating from Mendix 10 to 11 will retain the old String behavior unless you manually switch to the new one. |
Contributor
There was a problem hiding this comment.
new sting? I think you mean #new-string-behavior? 😄
| We recommend carefully analyzing all expressions that are comparing strings against `''` or `empty` and doing extensive testing after the migration. | ||
| In Mendix 11.6.3 we have introduced [an option](https://docs.mendix.com/refguide/app-settings/#new-sting-behavior) to toggle between the old and the new client-side String attribute behaviors. Projects migrating from Mendix 10 to 11 will retain the old String behavior unless you manually switch to the new one. | ||
|
|
||
| We recommend to migrate your pre-existing projects to use the new behavior as soon as possible. |
Contributor
There was a problem hiding this comment.
Should we provide them with reasons why to migrate as soon as possible? The old behavior will be available until Mendix 12. Why should I migrate? I think it's good to mention that the new behavior will improve consistency between nanoflows and microflows, which will lead to less bugs in customers applications? (Maybe this is already mentioned elsewhere)
| In Mendix 11.6.3 we have introduced [an option](https://docs.mendix.com/refguide/app-settings/#new-sting-behavior) to toggle between the old and the new client-side String attribute behaviors. Projects migrating from Mendix 10 to 11 will retain the old String behavior unless you manually switch to the new one. | ||
|
|
||
| We recommend to migrate your pre-existing projects to use the new behavior as soon as possible. | ||
| Please, make sure to carefully analyze all expressions that are comparing strings against `''` or `empty` and do extensive testing after the migration. |
Contributor
There was a problem hiding this comment.
Suggested change
| Please, make sure to carefully analyze all expressions that are comparing strings against `''` or `empty` and do extensive testing after the migration. | |
| Please make sure to carefully analyze all expressions that are comparing strings against `''` or `empty` and do extensive testing after the migration. |
| * **Yes**: Use the React client (default). In this mode, you will get consistency errors for incompatible widgets. | ||
| * **Migration mode**: Use the React client and ignore incompatible widgets. Placeholders are displayed in the case of incompatible widgets. Recommended when trying out the new client. | ||
|
|
||
| ### Use new string behavior {#new-sting-behavior} |
Contributor
There was a problem hiding this comment.
Oh you made the same typo here sting like a bee
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Added documentation for the new string behavior toggle and mentioned the toggle in the upgrade guide.