From d2831c9b2195252ea63f1e0dc306a3020ca740cb Mon Sep 17 00:00:00 2001 From: Jan Tychtl Date: Mon, 20 Apr 2026 09:16:29 +0200 Subject: [PATCH] chore: remove stray .claude memory file This personal Claude memory file was accidentally committed in a previous PR and is not project content. risk: nonprod --- .../memory/feedback_no_parent_chains.md | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 .claude/projects/-home-jenda-Desktop-GoodFolder-gooddata-python-sdk/memory/feedback_no_parent_chains.md diff --git a/.claude/projects/-home-jenda-Desktop-GoodFolder-gooddata-python-sdk/memory/feedback_no_parent_chains.md b/.claude/projects/-home-jenda-Desktop-GoodFolder-gooddata-python-sdk/memory/feedback_no_parent_chains.md deleted file mode 100644 index 1a67ad312..000000000 --- a/.claude/projects/-home-jenda-Desktop-GoodFolder-gooddata-python-sdk/memory/feedback_no_parent_chains.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -name: no-parent-chains -description: User dislikes chained .parent.parent.parent path navigation - considers it bad practice -type: feedback ---- - -Avoid chaining `.parent.parent.parent` for path resolution — it's fragile and hard to read. - -**Why:** The user called it "really stupid" and "bad practice." It's brittle when directory structure changes. - -**How to apply:** Use explicit path construction, environment variables, or package-relative resource loading instead of long `.parent` chains.