Skip to content

fix(core1): resolve CI stock type error and migrate sale APIs - #7

Open
danielitoCode wants to merge 11 commits into
masterfrom
fix/core1-ci-stock-and-deprecations
Open

fix(core1): resolve CI stock type error and migrate sale APIs#7
danielitoCode wants to merge 11 commits into
masterfrom
fix/core1-ci-stock-and-deprecations

Conversation

@danielitoCode

Copy link
Copy Markdown
Owner

Objective

Resolve the Core 1 CI compilation failure and remove the Appwrite Databases deprecation warnings reported by :shared-data:compileDebugKotlin.

Changes

  • Android stock atomic operations now adapt domain Int quantities to Appwrite's Double? API at the infrastructure boundary.
  • Android shared sales repository migrated from Databases document APIs to TablesDB row APIs.
  • Shared sales mapper migrated from Document to Row.
  • Android DI now provides TablesDB while preserving Databases for existing consumers.
  • Web sales repository migrated from Databases document APIs to TablesDB row APIs.
  • Web infrastructure exposes TablesDB and the sales container injects it.
  • Added the requested Core 1 agent log under .roadmap/Core 1/changes/AgentsLogs.

Validation intent

This PR is intentionally against master and must be validated by CI before production integration. The previous failure was caused by Int arguments passed to Appwrite atomic operations where the SDK expects Double?; the sale API warnings are also addressed.

Safety

No direct changes were made to master. Auto-merge is enabled so GitHub can merge only after the repository's required checks and merge conditions pass.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

Qodana for JVM

4 new problems were found

Inspection name Severity Problems
Unstable API Usage 🔶 Warning 4
View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.3.2
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant