Update form configs for cs-form-create, form-templates

[Lihlu]

Summary by CodeRabbit

• Chores
  • Internal configuration update to the project build system.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 250a8e74-5342-435f-98f2-6b2d33a7cfeb

📥 Commits

Reviewing files that changed from the base of the PR and between 9477a08 and ff497d8.

📒 Files selected for processing (2)

• shesha-core/src/Shesha.Application/ConfigMigrations/package20260311_1518.shaconfig
• shesha-core/src/Shesha.Application/Shesha.Application.csproj

---

Walkthrough

A configuration migration file (package20260311_1518.shaconfig) is transitioned from a non-embedded resource to an embedded resource in the Shesha.Application project file, changing how the file is compiled and packaged.

Changes

Cohort / File(s)	Summary
Project Resource Configuration shesha-core/src/Shesha.Application/Shesha.Application.csproj	Configuration migration file moved from None/Remove to EmbeddedResource/Include status, changing resource embedding behavior during compilation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update standard forms #4546: Modifies the same Shesha.Application.csproj resource entries, moving config .shaconfig files between None and EmbeddedResource groups.
• fix: add new configuration migration package20251113_1323.shaconfig #4201: Moves a ConfigMigrations .shaconfig file from "None Remove" to "EmbeddedResource Include" in the same project file using the same pattern.
• Update form configs #4587: Makes the same csproj change by moving ConfigMigrations/*.shaconfig files from "None Remove" to "EmbeddedResource" with different package filenames.

Suggested reviewers

• IvanIlyichev
• AlexStepantsov

Poem

🐰 A config file tucked so tight,
Embedded now, bundled just right,
From loose and free to nestled deep,
In resources where migrations sleep! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions updating form configs for specific forms, but the actual change is embedding a configuration file in the project. The title does not accurately describe the main technical change.	Revise the title to reflect the actual change, such as 'Embed form configuration file as resource' or similar, to better describe the ConfigMigrations package transition.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}