fix: ESLint config in app-store and features

[hbjORbj]

What does this PR do?

Current behavior:

• /features can import /app-store, but /app-store can't import /features. Currently, it's the other way around.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• N/A - I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Please use the latest Vercel preview and test please 🙏.

[coderabbitai]

Walkthrough

Updated packages/app-store/eslint.config.mjs to change the ESLint forbid rule’s exclusion from "../app-store/" to "../features/". This alters which paths are excluded from the restriction. No changes to exports or other config structure.

Possibly related PRs

• chore: eslint rule for blocking importing features from appstore, lib, prisma #23832: Adjusts ESLint import-restriction rules to modify blocked/excluded app-store/features paths, aligning with this PR’s rule change.
• chore: add an eslint rule to warn importing trpc package in app store package #23665: Updates ESLint config within the app-store package, specifically around import restrictions/exclusions similar to this change.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title directly references the correction to the ESLint configuration and identifies the relevant directories involved. It concisely describes the main focus of the changeset by noting both app-store and features contexts. This phrasing allows teammates scanning history to quickly grasp the primary purpose of the PR.
Description Check	✅ Passed	The description clearly outlines the current import behavior issue, includes a screenshot for context, and specifies how the ESLint configuration will be adjusted. It directly relates to the code modifications and provides sufficient instructions for testing. Therefore, the description appropriately supports and explains the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/eslint-configs

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 445b307 and 609fba2.

📒 Files selected for processing (1)

• packages/app-store/eslint.config.mjs (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Install dependencies / Yarn install & cache

🔇 Additional comments (1)

packages/app-store/eslint.config.mjs (1)

7-7: LGTM: no imports from ../features/** found in packages/app-store—safe to merge.

---

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

[github-actions]

E2E results are ready!

• Workflow #82568.1 latest results