You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-\[MenuButton\] Pass through AdditionalAttributes ([#3798](https://github.com/microsoft/fluentui-blazor/pull/3798))
21
+
-\[MenuProvider\] Pass through class and style from menu's. ([#3809](https://github.com/microsoft/fluentui-blazor/pull/3809))
22
+
-\[MultiSplitter\] Remove position from panel CSS ([#3870](https://github.com/microsoft/fluentui-blazor/pull/3870))
23
+
-\[SortableList\] Extend the CSS class with more predefined variables([#3877](https://github.com/microsoft/fluentui-blazor/pull/3877))
24
+
-\[Tabs\] Make initialization logic more robust ([#3878](https://github.com/microsoft/fluentui-blazor/pull/3878))
25
+
26
+
### Demo site and documentation
27
+
-\[Docs\] Add docs about `FluentEditForm` ([#3832](https://github.com/microsoft/fluentui-blazor/pull/3832))
28
+
-\[Docs\] Fix typo in InputFile documentation ([#3769](https://github.com/microsoft/fluentui-blazor/pull/3769))
29
+
-\[Docs\] Fix typo in Card documentation ([#3839](https://github.com/microsoft/fluentui-blazor/pull/3839))
30
+
-\[Docs\] Remove Autofocus to prevent scrolling in the docs (#3826) ([#3828](https://github.com/microsoft/fluentui-blazor/pull/3828))
31
+
-\[Docs\] Update reboot section for IIS hosting workaround ([#3788](https://github.com/microsoft/fluentui-blazor/pull/3788))
32
+
33
+
### Icons and Emoji
34
+
- Update to Fluent UI System Icons 1.1.302.
35
+
See the commit history in the Fluent UI System Icons repository [commit history](https://github.com/microsoft/fluentui-system-icons/commits/main/) for the full list of changes.
Copy file name to clipboardExpand all lines: docs/contributing.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,11 +38,17 @@ dotnet build
38
38
39
39
### Submitting a pull request
40
40
41
-
If you'd like to contribute by fixing a bug, implementing a feature, or even correcting typos in our documentation, you'll want to submit a pull request. Before submitting a pull request, be sure to [rebase](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) your branch from master. Do not use ``git merge`` or the *merge* button provided by GitHub.
41
+
If you'd like to contribute by fixing a bug, implementing a feature, or even correcting typos in our documentation, you'll need to submit a pull request.
42
+
Before submitting a pull request, be sure to [rebase](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) your branch from master. Do not use ``git merge`` or the *merge* button provided by GitHub.
42
43
43
-
### Merging a pull request
44
+
For PR naming use the following convention: `[component name] Description` (note no period at the end)
44
45
45
-
If you are merging a pull request, be sure to use the pull request title as the commit title. The title should follow the [conventional commit guidelines](https://www.conventionalcommits.org/). It is recommended that if you are merging in pull requests regularly that you add a browser extension that will auto-correct the title for you. A few that should do this are [Refined GitHub](https://github.com/sindresorhus/refined-github) and [Squashed Merge Message](https://github.com/zachwhaley/squashed-merge-message).
46
+
- For the component name, leave out the Fluent part.
47
+
- For the description, do not reference an issue number in there. Just a clear, short summary of what change entails is enough. There is enough room to elaborate in the description .
48
+
49
+
When a PR is related to an issue, use the 'fix #issuenumber' syntax to automatically link the issue to the PR. That way the issue gets closed when the PR is merged.
50
+
51
+
For PR description use before and after images /screenshot when possible to make more clear what has changed. We link to the PRs from the what's new page so it helps to provide better context.
Copy file name to clipboardExpand all lines: examples/Demo/Shared/Microsoft.FluentUI.AspNetCore.Components.xml
+33Lines changed: 33 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1241,6 +1241,12 @@
1241
1241
If not specified, the default header template includes the <see cref="P:Microsoft.FluentUI.AspNetCore.Components.ColumnBase`1.Title" /> along with any applicable sort indicators and options buttons.
Gets or sets a <see cref="T:Microsoft.AspNetCore.Components.RenderFragment" /> that will be rendered for this column's header title.
1362
+
This allows derived components to change the header title output. However, derived components are then
1363
+
responsible for using <see cref="P:Microsoft.FluentUI.AspNetCore.Components.ColumnBase`1.HeaderCellTitleTemplate" /> within that new output if they want to continue
By default a card restricts its content to the card area. This means, for exmple, that if you have a select list with a lot of items, the list will be cut off at the bottom of the card.
19
+
By default a card restricts its content to the card area. This means, for example, that if you have a select list with a lot of items, the list will be cut off at the bottom of the card.
20
20
You can override this behavior by setting the <code>AreaRestricted</code> property to <code>false</code>.
Copy file name to clipboardExpand all lines: examples/Demo/Shared/Pages/DataGrid/DataGridPage.razor
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@
58
58
<h2id="sorting">Sorting</h2>
59
59
<p>
60
60
The DataGrid supports sorting by clicking on the column headers. The default sort direction is ascending. Clicking on the same column header again will toggle the sort direction.
61
-
A sort can be removed by right clicking on the header column (with exception of the default sort).
61
+
A sort can be removed by right clicking (or by pressing Shift+R) on the header column (with exception of the default sort).
0 commit comments