Skip to content

Commit 08215b4

Browse files
quinntracyquinntracy
authored
Merge branch 'development' into ufc/2094-rspack-ga
2 parents ed37a8f + ac872bc commit 08215b4

413 files changed

Lines changed: 14028 additions & 523 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.claude/skills/docs-polish/SKILL.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,8 @@ Improve clarity and readability without changing meaning, structure, or paragrap
2020
* Simplify wordy or awkward phrasing
2121
* Improve word choice (more precise or accessible terms)
2222
* Change passive voice to active voice where appropriate
23-
* Remove bold and italics used for emphasis (reword or use alerts if needed)
23+
* Remove first-person plural (we, us, our, let's), except in release notes
24+
* Remove bold and italics used for emphasis (reword or use alert shortcodes if needed)
2425
* Apply Mendix style guide standards (overrides the Microsoft Writing Style Guide)
2526
* Apply Microsoft Writing Style Guide standards, unless they conflict with the Mendix style guide standards
2627

‎.claude/skills/docs-proofread/SKILL.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Do NOT:
2222
* Change passive voice to active voice
2323
* Simplify complex sentences
2424
* Reorganize content
25+
* Remove Markdown comments
2526

2627
Priority order for determining scope:
2728
1. If the user has selected text in a file (check for `ide_selection` tags), only proofread the selected text in that file. Don't proofread the entire document.

‎.github/workflows/auto-assign-pr.yml‎

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
name: Auto-assign PR to Technical Writers
2+
3+
on:
4+
pull_request:
5+
types: [opened]
6+
7+
jobs:
8+
auto-assign:
9+
runs-on: ubuntu-latest
10+
permissions:
11+
pull-requests: write
12+
13+
steps:
14+
- name: Assign PR to creator if on Technical Writers team
15+
uses: actions/github-script@v7
16+
with:
17+
script: |
18+
const creator = context.payload.pull_request.user.login;
19+
const prNumber = context.payload.pull_request.number;
20+
const assignees = context.payload.pull_request.assignees;
21+
22+
// Technical Writers team members
23+
const techWriters = [
24+
'ConnorLand',
25+
'Karuna-Mendix',
26+
'MariaShaposhnikova',
27+
'MarkvanMents',
28+
'NicoletaComan',
29+
'OlufunkeMoronfolu',
30+
'Yiyun333',
31+
'dbreseman',
32+
'katarzyna-koltun-mx',
33+
'quinntracy'
34+
];
35+
36+
console.log(`Processing PR #${prNumber} by ${creator}`);
37+
console.log(`Current assignees: ${assignees.length > 0 ? assignees.map(a => a.login).join(', ') : 'none'}`);
38+
39+
if (assignees.length > 0) {
40+
console.log('PR already has assignees, skipping auto-assignment');
41+
return;
42+
}
43+
44+
if (techWriters.includes(creator)) {
45+
console.log(`${creator} is on technical writers team, assigning PR...`);
46+
await github.rest.issues.addAssignees({
47+
owner: context.repo.owner,
48+
repo: context.repo.repo,
49+
issue_number: prNumber,
50+
assignees: [creator]
51+
});
52+
console.log(`Successfully assigned PR #${prNumber} to ${creator}`);
53+
} else {
54+
console.log(`${creator} is not on technical writers team, skipping assignment`);
55+
}

‎CLAUDE.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,7 @@ Before creating a new file, use Glob to explore the directory structure and unde
7676

7777
* **Guiding manual** – Mendix-specific style guides (see subsection below) extend and customize the Microsoft Writing Style Guide (https://learn.microsoft.com/style-guide/). Consult the Mendix style guides first for grammar, inclusive language, terminology, and formatting rules; use MSG as fallback for topics not covered by Mendix guides.
7878
* **Tone** – Clear, concise, active voice; use imperative mood for procedures; second person (you/your) when addressing readers. Keep a conversational, straightforward tone. Present tense. Use American English and write for a global audience. Prefer short, everyday words; avoid or explain jargon. Keep it simple—short sentences and fragments are easier to scan and read, and prune excess words. Avoid marketing language.
79+
* **Person** – Avoid first-person plural (we, us, our, let's) in all documentation except release notes.
7980
* **Terminology** – Capitalize product names (Mendix, Studio Pro, Developer Portal); use "microflow", "nanoflow", etc. consistently. Never use e.g. or i.e.
8081
* **Text formatting** – Reserve bold for UI labels, button names, menu items, or other interface text, or for introductions in list items. Don't use italics except to refer to titles and sections. Use wording or alert shortcodes for emphasis; don't use text formatting for emphasis. Use code font only to wrap literal code, filenames, paths, or command-line input. Use `<kbd>` for keyboard shortcuts.
8182
* **Headings** – H1 is generated from the front‑matter title. Subsequent headings increment by one level at a time. Don't use bold or italics as a replacement for headings. Use title case. Never start headings with numerals.

‎assets/scss/_front-page.scss‎

Lines changed: 55 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,31 +2,68 @@
22

33
.td-main main.lp {
44
padding: 2rem 2.5rem;
5-
padding-top:5.25rem !important;
5+
padding-top: 0 !important; // top clearance handled by lp-mobile-bar (mobile) and lp-hero (desktop)
6+
7+
@include media-breakpoint-up(md) {
8+
padding-top: 0 !important;
9+
}
610
}
711

812
div.lp-container {
913
padding: 0;
1014
margin: 0;
15+
max-width: none;
1116
}
1217

1318
.lp-row{
1419
margin-bottom: 2rem !important;
1520
}
1621

22+
.lp-hero {
23+
background-color: $dark;
24+
min-height: 350px;
25+
margin-left: -2.5rem;
26+
margin-right: -2.5rem;
27+
padding: 2rem 2.5rem;
28+
29+
@include media-breakpoint-down(md) {
30+
min-height: unset;
31+
}
32+
}
33+
34+
.hero-text {
35+
flex: 0 0 100%;
36+
// Stretch out text once image disappears (smaller viewports)
37+
@include media-breakpoint-up(lg) {
38+
flex: 0 0 auto;
39+
max-width: 60%;
40+
}
41+
}
42+
1743
h1.page-title {
1844
font-weight: $font-weight-normal;
1945
font-size: 2rem;
20-
margin-bottom: 0.75rem;
46+
margin-bottom: 1rem;
2147
}
2248

2349
h5.lp-description {
2450
font-size: 1rem;
2551
font-weight: 400;
52+
line-height: 1.5;
2653
}
2754

2855
.lp-container img {
2956
border-style: none;
57+
max-width: 100%;
58+
height: auto;
59+
}
60+
61+
.lp-container .hero-image img {
62+
height: 220px;
63+
width: auto;
64+
max-width: unset;
65+
flex-shrink: 0;
66+
3067
}
3168

3269
img.card-icon {
@@ -99,3 +136,19 @@ p.rn-date {
99136
font-weight: 400;
100137
margin-bottom: 0rem;
101138
}
139+
140+
// Mobile hamburger bar on landing page — matches hero background
141+
.lp-mobile-bar {
142+
background-color: $dark;
143+
margin-left: -2.5rem;
144+
margin-right: -2.5rem;
145+
padding: 4rem 2.5rem 0.75rem;
146+
color: white;
147+
148+
.btn {
149+
color: white;
150+
font-size: 0.75rem;
151+
font-weight: 400;
152+
margin-bottom: 0rem;
153+
}
154+
}

‎assets/scss/_variables_project.scss‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,14 @@ $enable-shadows: true; //TODO: consider removing this duplicate variable from th
1111

1212
$primary: #146FF4; // MX Blue (Blue-7 from PDS) YL - updated the Mendix Blue color to its latest version in MX 10
1313
$primary-light: #47A9FF; // DB - Blue-5 from PDS
14-
$secondary: #0A1325; // Gray-10 from PDS (MxDock color)
14+
$secondary: #0A1324; // Gray-10 from PDS (MxDock color)
1515
$success: #0D990D; // DB - Green-8 from PDS
1616
$info: #146FF4; // MX Blue YL - updated the Mendix Blue color to its latest version in MX 10
1717
$warning: #C97800; // DB - Yellow-8 from PDS
1818
$danger: #D31E23; // DB - Red-7 PDS
1919
$white: #fff; // YL - Override the default color defined in _variables_forward.scss
2020
$light: #99D0FF; // DB - Blue-3 from PDS
21-
$dark: #0A1325; // Gray-10 from PDS (MxDock color)
21+
$dark: #0A1324; // Gray-10 from PDS (MxDock color)
2222
$blue: #146FF4; // YL - Mendix Blue in SP 10; Override the default color defined in _variables_forward.scss
2323
$company-approved: #E0FAE1; // NC - Company approved Marketplace label
2424
$gray-100: #f7f7f7;

‎content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/deploy-api.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "Private Mendix Platform Deploy API"
3+
url: /apidocs-mxsdk/apidocs/private-platform-deploy-api/
4+
type: swagger
5+
description: "This API allows you to create and manage environments in Private Mendix Platform."
6+
restapi: true
7+
weight: 60
8+
linktitle: "Deploy API"
9+
---
10+
11+
{{% alert color="info" %}}
12+
This document is about [Private Mendix Platform](/private-mendix-platform/) API. This API is only available on instances of Private Mendix Platform. For [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) API, see [Mendix on Kubernetes Build API](/apidocs-mxsdk/apidocs/private-cloud-build-api/) and [Mendix on Kubernetes Deploy API](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/).
13+
{{% /alert %}}
14+
15+
## Introduction
16+
17+
The Private Mendix Platform Group API allows you to manage environments in Private Mendix Platform. You can use the API to do the following:
18+
19+
* Create a new environment for the application
20+
* Retrieve all environments for the application
21+
* Retrieve a specified environment for the application
22+
* Update a specified environment for the application
23+
* Delete a specified environment for the application
24+
25+
## API Reference
26+
27+
{{< swaggerui src="/openapi-spec/openapi-deploy.yaml" >}}

‎content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/pluggable-widgets-property-types.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -775,7 +775,7 @@ When the property is defined as follows:
775775

776776
Then the Studio Pro UI for the property appears like this:
777777

778-
{{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource.png" class="no-border" >}}
778+
{{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource-list.png" class="no-border" >}}
779779

780780
### Selection {#selection}
781781

‎content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md‎

Lines changed: 64 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@ This defines a property's type. A `type` must be one of the following:
5959
* [object](#object)
6060
* [file](#file)
6161
* [datasource](#datasource)
62+
* [List data source](#list-datasource)
63+
* [Object data source](#object-datasource)
6264
* [selection](#selection)
6365

6466
### XML Elements
@@ -480,9 +482,6 @@ Then the Studio Pro UI for the property appears like this:
480482

481483
### Action {#action}
482484

483-
{{% alert color="info" %}}
484-
The `defaultType` and `defaultValue` attributes for Action were introduced in Mendix [10.15](/releasenotes/studio-pro/10.15/).
485-
{{% /alert %}}
486485

487486
The action property type allows a user to configure an action which can do things like call nanoflows, save changes, and open pages.
488487

@@ -746,41 +745,37 @@ Then the Studio Pro UI for the property appears like this:
746745

747746
### Datasource {#datasource}
748747

749-
The datasource property allows widgets to work with object lists. The client component will receive value prop of type [`ListValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listvalue) and may be used with [`action`](#action), [`attribute`](#attribute), [`association`](#association), [`expression`](#expression), [`text template`](#texttemplate), and [`widgets`](#widgets) properties. See [Data Sources](/refguide/data-sources/#list-widgets) for available data source types.
748+
The datasource property allows widgets to work with data from the Mendix Platform. It comes in two variants controlled by the `isList` attribute: a **list data source** (`isList="true"`) for working with collections of objects, and an **object data source** (`isList="false"`) for working with a single object.
750749

751750
If no data source has been configured by the user, any properties that are linked to the datasource property are automatically omitted from the props passed to the client component (even if they are marked as required).
752751

753-
{{% alert color="warning" %}}
754-
Only list datasources are supported, therefore specifying `isList="true"` is required.
755-
{{% /alert %}}
756-
757752
#### XML Attributes
758753

759754
| Attribute | Required | Attribute Type | Description |
760755
|----------------|----------|----------------|------------------------------------------------------------------------------------------------------------|
761756
| `type` | Yes | String | Must be `datasource` |
762757
| `key` | Yes | String | See [key](#key) |
763-
| `isList` | Yes | Boolean | Must be `true` |
758+
| `isList` | Yes | Boolean | `true` for a list data source, `false` for an object data source |
764759
| `required` | No | Boolean | This decides if the user is required to specify a datasource, `true` by default |
765-
| `defaultType` | No | String | Default type for the property, supported values are `Database`, `Microflow`, `Nanoflow`, and `Association` |
760+
| `defaultType` | No | String | Default type for the property, see [Default Data Sources](#data-source-defaults) |
766761
| `defaultValue` | No | String | Default value for the property, see [Default Data Sources](#data-source-defaults) |
767762

768763
##### Data Source Defaults {#data-source-defaults}
769764

770-
{{% alert color="info" %}}
771-
The `defaultType` and `defaultValue` attributes for datasources were introduced in Mendix [10.16](/releasenotes/studio-pro/10.16/).
772-
{{% /alert %}}
773-
774765
You can use the `defaultType` and `defaultValue` attributes to configure default data sources for your widget. Unless overridden in Studio Pro, the widget will attempt to configure the data source according to its defaults. Both attributes need to be set for the defaults to be applied.
775766

776767
The format of `defaultValue` depends on the chosen `defaultType`:
777768

778-
| Data source type | Format | Example |
779-
|--------------------------|-------------|-----------------------------------------------------------------------|
780-
| `Database` `Association` | Entity Path | `ModuleName.EntityName` or `ModuleName.A/ModuleName.A_B/ModuleName.B` |
781-
| `Microflow` `Nanoflow` | Document ID | `ModuleName.DocumentName` |
769+
| Data source type | Format | Example | Supported For |
770+
|--------------------------|-------------|-----------------------------------------------------------------------|------------------------------------|
771+
| `Database` `Association` | Entity Path | `ModuleName.EntityName` or `ModuleName.A/ModuleName.A_B/ModuleName.B` | List data source |
772+
| `Microflow` `Nanoflow` | Document ID | `ModuleName.DocumentName` | List and object data source |
782773

783-
#### Studio Pro UI
774+
#### List Data Source {#list-datasource}
775+
776+
A list data source (`isList="true"`) allows a widget to work with a collection of objects. The client component receives a prop of type [`ListValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listvalue). For more information on available data source type, see [Data Sources](/refguide/data-sources/#list-widgets).
777+
778+
##### Studio Pro UI
784779

785780
When the property is defined as follows:
786781

@@ -793,14 +788,57 @@ When the property is defined as follows:
793788

794789
Then the Studio Pro UI for the property appears like this:
795790

796-
{{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource.png" class="no-border" >}}
791+
{{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource-list.png" class="no-border" >}}
797792

798-
### Selection {#selection}
793+
#### Object Data Source {#object-datasource}
799794

800795
{{% alert color="info" %}}
801-
The property type was introduced in Mendix [10.7](/releasenotes/studio-pro/10.7/).
796+
The object data source was introduced in Mendix [11.11](/releasenotes/studio-pro/11.11/).
802797
{{% /alert %}}
803798

799+
An object data source (`isList="false"`) allows a widget to work with a single object. The client component receives a prop of type [`DynamicValue<ObjectItem>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value).
800+
801+
A widget may have, at maximum, **one** object data source property.
802+
803+
The available source types differ from list data sources:
804+
805+
| Platform | Available Source Types |
806+
|----------|-----------------------------------------------------------|
807+
| Web | Context, Microflow, Nanoflow, Listen to widget |
808+
| Native | Context, Microflow, Nanoflow |
809+
810+
##### Studio Pro UI
811+
812+
When the property is defined as follows:
813+
814+
```xml
815+
<property key="data" type="datasource" isList="false" required="false">
816+
<caption>Data source</caption>
817+
<description />
818+
</property>
819+
```
820+
821+
Then the Studio Pro UI for the property appears like this:
822+
823+
{{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource-single-object.png" class="no-border" >}}
824+
825+
#### Linking Properties to Data Sources {#datasource-linking}
826+
827+
The [`action`](#action), [`attribute`](#attribute), [`association`](#association), [`expression`](#expression), [`text template`](#texttemplate), [`widgets`](#widgets), and [`selection`](#selection) properties can be linked to a data source using the `dataSource` attribute on those properties. The client type received by the component depends on the data source type:
828+
829+
| Property type | List data source client type | Object data source client type |
830+
|:---------------|:-----------------------------|:--------------------------------------|
831+
| `action` | [`ListActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listactionvalue) | [`ActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#action-value) |
832+
| `attribute` | [`ListAttributeValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listattributevalue) | [`EditableValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#editable-value) |
833+
| `association` | [`ListReferenceValue` or `ListReferenceSetValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listassociationvalue) | `ReferenceValue` or `ReferenceSetValue` |
834+
| `expression` | [`ListExpressionValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listexpressionvalue) | [`DynamicValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value) |
835+
| `textTemplate` | [`ListExpressionValue<string>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listexpressionvalue) | [`DynamicValue<string>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value) |
836+
| `widgets` | [`ListWidgetValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listwidgetvalue) | `ReactNode` |
837+
| `selection` | `SelectionSingleValue` or `SelectionMultiValue` | *Not supported* |
838+
839+
### Selection {#selection}
840+
841+
804842
The selection property allows a widget to read and set a selection that can be used in actions, expressions, or a `Listen to` data source of a data view.
805843

806844
#### XML Attributes
@@ -813,6 +851,10 @@ The selection property allows a widget to read and set a selection that can be u
813851
| `defaultValue` | No | String (Expression) | Default value for the property |
814852
| `onChange` | No | Property Path | The path to an [`action`](#action) property that will be run by the Mendix Platform when the selection is changed by the widget |
815853

854+
{{% alert color="warning" %}}
855+
The `dataSource` attribute must refer to a [list data source](#list-datasource). Linking a selection property to an object data source is not supported.
856+
{{% /alert %}}
857+
816858
#### XML Elements
817859

818860
`<selectionTypes>` (required) — This element encapsulates `<selectionType>` elements which declare supported selection types available while configuring the selection property in Studio Pro.
@@ -867,9 +909,6 @@ Label property allows a pluggable widget to have labeling functionality similar
867909

868910
#### setLabel {#setLabel}
869911

870-
{{% alert color="info" %}}
871-
The `setLabel` attribute was introduced in Mendix [10.5](/releasenotes/studio-pro/10.5/).
872-
{{% /alert %}}
873912

874913
You can use `setLabel` to specify which properties can be used to set the `Label` property value.
875914

0 commit comments

Comments
 (0)