Enforce canonical field order in Social Web feed DataViews

[pfefferle]

Enforces canonical field order in the Social Web feed DataViews to ensure fields always display in the same order regardless of user toggling field visibility. When a user hides and re-shows a field, it now returns to its original position instead of being appended to the end.

Problem

When users toggle field visibility in DataViews, the view.fields array gets modified. If a user hides a field and then shows it again, DataViews appends it to the end of the array instead of returning it to
its original position. This causes the field order to become inconsistent and break the intended display order.

Solution

Implements field order normalization by:

1. Defining a canonical field order in the fields array: metadata → title → excerpt → content → date
2. Creating a normalizedView that sorts view.fields according to the canonical order
3. Using a Map to track each field's position in the canonical order
4. Sorting visible fields to match that order, regardless of when they were toggled on/off

Proposed changes

• Add field order normalization logic using useMemo
• Create normalizedView that maintains canonical field order
• Use normalizedView in DataViews component instead of raw view
• Rebuild JavaScript assets

Example

Before:

1. User sees: metadata, title, excerpt
2. User hides title
3. User hides excerpt
4. User shows excerpt → Result: metadata, excerpt (wrong order)
5. User shows title → Result: metadata, excerpt, title (wrong order)

After:

1. User sees: metadata, title, excerpt
2. User hides title
3. User hides excerpt
4. User shows excerpt → Result: metadata, excerpt (correct)
5. User shows title → Result: metadata, title, excerpt (correct - maintains canonical order)

Other information:

• Have you written new tests for your changes, if applicable?

Testing instructions:

• Build completes successfully
• Fields display in canonical order: metadata, title, excerpt, content, date
• Hiding and re-showing fields maintains canonical order
• Field visibility preferences still persist via useView hook

Changelog entry

• Automatically create a changelog entry from the details below.

Changelog Entry Details

Significance

• Patch
• Minor
• Major

Type

• Added - for new features
• Changed - for changes in existing functionality
• Deprecated - for soon-to-be removed features
• Removed - for now removed features
• Fixed - for any bug fixes
• Security - in case of vulnerabilities

Message

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.