Update form configs

[Lihlu]

Epdated form configs for cs-folder-create, cs-notification-type-create, forgot-password, login, modules, registration and user-details

Summary by CodeRabbit

• Chores
  • Updated configuration file handling in the application build process.

[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: 5e14154e-a9c2-440a-9721-dd6a6c058889

📥 Commits

Reviewing files that changed from the base of the PR and between 7097309 and 6aea89f.

📒 Files selected for processing (2)

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

---

Walkthrough

The change relocates a configuration migration package file (package20260310_1617.shaconfig) from the None Remove list to the EmbeddedResource Include list in the Shesha.Application project file, ensuring proper resource embedding.

Changes

Cohort / File(s)	Summary
Project Configuration shesha-core/src/Shesha.Application/Shesha.Application.csproj	Moved ConfigMigrations shaconfig file from None Remove to EmbeddedResource Include to ensure proper resource embedding.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: add new configuration migration package20251113_1323.shaconfig #4201: Same configuration change pattern applied to a different timestamped ConfigMigrations .shaconfig file.
• Update Notification Types Config form #4427: Identical code-level change moving a differently-named ConfigMigrations package from None to EmbeddedResource.
• chore: migrating the header, reference-list-item-edit and reference-l… #3885: Related project file modification following the same ConfigMigrations file relocation pattern.

Suggested reviewers

• IvanIlyichev

Poem

🐰 A config file hops from None to light,
Embedded now, bundled just right,
Migration twenty-six takes flight—
Resources bundled, packaged tight! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update form configs' is vague and generic, using non-descriptive language that doesn't convey meaningful information about which specific form configurations were updated or what changes were made.	Consider a more specific title that references the actual forms updated (e.g., 'Update form configurations for folder creation, notifications, and user details') or the nature of the changes made.

✅ 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

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.}