Skip to content

Simplify pinned-column wording, preserve demo page metadata, and remove tracked generated props file#4673

Draft
Copilot wants to merge 8 commits intocopilot/research-fluentdatagrid-implementationfrom
copilot/update-pinoffsetpx-value
Draft

Simplify pinned-column wording, preserve demo page metadata, and remove tracked generated props file#4673
Copilot wants to merge 8 commits intocopilot/research-fluentdatagrid-implementationfrom
copilot/update-pinoffsetpx-value

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 4, 2026

Pull Request

📖 Description

This PR updates the pinned-columns documentation to use plain start / end wording, preserves the demo page metadata required for the demo site navigation, and removes an accidentally tracked generated file under src/Core.Scripts/obj.

  • Pinned column docs/comments

    • Reword XML comments, markdown docs, and test comments to avoid inline-start, inline-end, inset-inline-start, and inset-inline-end
    • Keep the public guidance focused on Start / End semantics, while preserving current runtime behavior
    • Restore the markdown front matter on the pinned-columns demo page so it remains registered in the demo site nav menu
    • Simplify the pinned-columns notes so they stay user-focused and avoid unnecessary implementation detail
  • Generated file cleanup

    • Remove src/Core.Scripts/obj\Debug/\package.g.props from source control
/// The column is pinned to the start edge of the grid.
/// The column will remain visible when the user scrolls toward the end.

🎫 Issues

  • Cleans up user-facing wording for pinned column documentation and comments
  • Preserves the demo page metadata required by the demo navigation
  • Removes an unintended generated artifact from the repo

👩‍💻 Reviewer Notes

Review the pinned-columns documentation updates and the single-file repository cleanup. No behavioral change is intended.

📑 Test Plan

  • Targeted pinned-column validation was performed for the wording updates
  • Attempted to build the demo project after restoring packages
  • The demo build surfaced an unrelated pre-existing BLAZOR106 error for examples/Demo/FluentUI.Demo.Client/Documentation/General/Spacing/Examples/SpacingComputedBoxes.razor.js
  • Generated file removal is repository hygiene only

✅ Checklist

General

  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

  • I have added a new component
  • I have added Unit Tests for my new component
  • I have modified an existing component
  • I have validated the Unit Tests for an existing component

MCP Server

  • I have added or updated MCP Server tools/prompts/resources
  • I have added Unit Tests for my MCP Server changes

⏭ Next Steps

  • None.

Copilot AI and others added 5 commits April 4, 2026 09:38
…x to PinOffset (string) with logical CSS properties

Agent-Logs-Url: https://github.com/microsoft/fluentui-blazor/sessions/705a5b7c-1768-42a0-ba5f-faa99daf78d4

Co-authored-by: vnbaaij <1761079+vnbaaij@users.noreply.github.com>
Comment on lines -1 to -5
---
title: Pinned columns
order: 0095
route: /DataGrid/PinnedColumns
---
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to stay in place. Is used for the demo site nav menu

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in a0f46eb by restoring the page front matter (title and route) so the demo nav/menu registration stays intact.

Comment on lines +61 to +62
* Column resizing interacts correctly with sticky offsets — the JavaScript in
`FluentDataGrid.razor.ts` recalculates `left` / `right` values after every resize step via
`FluentDataGrid.razor.ts` recalculates start and end offset values after every resize step via
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is too much detail. It is not necessary for the developer using the component to know this

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in a0f46eb to remove the implementation detail and keep the note user-focused.

Copilot AI and others added 2 commits April 4, 2026 15:53
Copilot AI changed the title Simplify pinned-column wording to start/end and remove tracked generated props file Simplify pinned-column wording, preserve demo page metadata, and remove tracked generated props file Apr 4, 2026
Copilot AI requested a review from vnbaaij April 4, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants