Repository navigation
Fix errors for expandable table shortcode - #12186
Merged
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| | <a id="commendixcoreSessionIdCookieName" href="#commendixcoreSessionIdCookieName">com.<wbr>mendix.<wbr>core.<wbr>SessionIdCookieName</a> | Defines the name of the cookie value which represents the session ID. Can be useful to change when running in a container which assumes a certain name for the session cookie. | XASSESSIONID | | ||
| | <a id="commendixcoreStorageService" href="#commendixcoreStorageService">com.<wbr>mendix.<wbr>core.<wbr>StorageService</a> | Defines which storage service module will be used. The storage service module takes care of storing the actual files associated with `System.FileDocument` objects, such as uploaded files. Possible values are `com.mendix.storage. localfilesystem`, `com.mendix.storage.s3`, and `com.mendix.storage.azure`. | com.<wbr>mendix.<wbr>storage.<wbr>localfilesystem | | ||
| | <a id="commendixcoreUseMimeDecoderForBase64" href="#commendixcoreUseMimeDecoderForBase64">com.<wbr>mendix.<wbr>core.<wbr>UseMimeDecoderForBase64</a> | The setting defines whether to use the Basic decoder ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648)) or MIME decoder ([RFC 2045](https://datatracker.ietf.org/doc/html/rfc2045)) when decoding base64 binary data. The Basic decoder is recommended due to its strictness in not accepting any character outside the Base64 specification, see [Security Considerations](https://datatracker.ietf.org/doc/html/rfc4648#section-12). This setting exists for reasons of backward compatibility. <br/>{{% alert color="warning" %}}Using the MIME decoder is deprecated and the option will be removed in future versions.{{% /alert %}} | false | | ||
| | <a id="commendixcoreUseMimeDecoderForBase64" href="#commendixcoreUseMimeDecoderForBase64">com.<wbr>mendix.<wbr>core.<wbr>UseMimeDecoderForBase64</a> | The setting defines whether to use the Basic decoder ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648)) or MIME decoder ([RFC 2045](https://datatracker.ietf.org/doc/html/rfc2045)) when decoding base64 binary data. The Basic decoder is recommended due to its strictness in not accepting any character outside the Base64 specification, see [Security Considerations](https://datatracker.ietf.org/doc/html/rfc4648#section-12). This setting exists for reasons of backward compatibility. <br/><div class="alert alert-warning">Using the MIME decoder is deprecated and the option will be removed in future versions.</div> | false | |
Contributor
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Mendix.Capitalization] Use ''Mendix'' (capitalized)
| | <a id="commendixstorages3ResourceNamePrefix" href="#commendixstorages3ResourceNamePrefix">com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>ResourceNamePrefix</a> | Prefix for the keys under which objects are stored. Separators are not added automatically to keys. For keys like `prefix/key1`, `com.mendix.storage.s3.ResourceNamePrefix` should have value `prefix/`. | | | ||
| | <a id="commendixstorages3ResourceNameSuffix" href="#commendixstorages3ResourceNameSuffix">com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>ResourceNameSuffix</a> | Suffix for the keys under which objects are stored. This can be used when S3 buckets are divided into different segments for different users with different credentials (for example, store objects as `[key].customer1` for customer1 and as `[key].customer2` for customer2). Separators are not added automatically to keys. For keys like `key1.customer1`, `com.mendix.storage.s3.ResourceNameSuffix` should have value `.customer1`. | | | ||
| | <a id="commendixstorages3Region" href="#commendixstorages3Region">com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>Region</a> | Sets the region in which the S3 bucket is located. This will be used to determine the service endpoint, unless overridden in **com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>EndPoint**. This setting will also be used as the signing region for requests.<br/><br/>In Mendix version 11.6.0 and above, this setting is mandatory. The runtime will not start if this setting is not configured. {{% alert color="warning" %}}Using an incorrect region can lead to the following errors:<br/><br/>`Unable to load region from any of the providers in the chain.`<br/><br/>`The bucket you are attempting to access must be addressed using the specified endpoint.`<br/><br/>`The authorization header is malformed; the region 'us-east-1' is wrong.`{{% /alert %}} | | | ||
| | <a id="commendixstorages3Region" href="#commendixstorages3Region">com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>Region</a> | Sets the region in which the S3 bucket is located. This will be used to determine the service endpoint, unless overridden in **com.<wbr>mendix.<wbr>storage.<wbr>s3.<wbr>EndPoint**. This setting will also be used as the signing region for requests.<br/><br/>In Mendix version 11.6.0 and above, this setting is mandatory. The runtime will not start if this setting is not configured. <div class="alert alert-warning">Using an incorrect region can lead to the following errors:<br/><br/>`Unable to load region from any of the providers in the chain.`<br/><br/>`The bucket you are attempting to access must be addressed using the specified endpoint.`<br/><br/>`The authorization header is malformed; the region 'us-east-1' is wrong.`</div> | | |
Contributor
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Mendix.Capitalization] Use ''Mendix'' (capitalized)
Collaborator
Author
|
expandable-table shortcode: support multi-line shortcode output in table cells Problem: Shortcodes such as alert and figure expand to multi-line HTML before expandable-table renders its content. A pipe-table row must be on one line, so the table ended at the first alert or figure, and the remaining rows showed as plain text. |
MarkvanMents
approved these changes
Nov 4, 2026
MarkvanMents
left a comment
MarkvanMents
left a comment
Collaborator
There was a problem hiding this comment.
Hi Karuna,
Thanks for the quick fix. I didn't think you would do it this quickly!
Looks great.
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
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.
https://mendix.atlassian.net/browse/TW-2751