Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .aios-core/core/execution/predictive-pipeline.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
// Retrocompatible wrapper — canonical source in .aiox-core/
module.exports = require('../../../.aiox-core/core/execution/predictive-pipeline');
Comment on lines +1 to +2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Use the repo's absolute import path in the compat shim.

This wrapper is a long-lived compatibility entry point, so the ../../../.aiox-core/... hop is brittle and breaks the project import rule.

As per coding guidelines, "**/*.{js,jsx,ts,tsx}: Use absolute imports instead of relative imports in all code`."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.aios-core/core/execution/predictive-pipeline.js around lines 1 - 2, Replace
the brittle relative require in the compat shim with the repo's absolute import
path: update the line in predictive-pipeline.js that currently does
module.exports =
require('../../../.aiox-core/core/execution/predictive-pipeline'); to use the
absolute import (for example module.exports =
require('.aiox-core/core/execution/predictive-pipeline') or the project's
configured package alias), leaving module.exports intact so the file remains a
retrocompat wrapper.

Loading
Loading