-
Notifications
You must be signed in to change notification settings - Fork 0
experimental fix #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR implements an experimental fix to update the TRPC client integration and ERP modules by switching to lumos-ts services, thereby streamlining authentication and order management along with ERP connectivity.
- Replaces the TRPC proxy client with a lumos-ts based TRPC client and re-exports integrated login and order services.
- Updates ERP router endpoints by adding explicit input type annotations and revises import sources to use lumos-ts.
- Introduces minor client-side adjustments for browser compatibility via process polyfill.
Reviewed Changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/utils/trpc.ts | Removes old TRPC proxy usage and uses lumos-ts client integration, re-exporting services. |
| src/modules/erp.ts | Adjusts ERP router endpoints with explicit input type annotations and uses lumos-ts imports. |
| src/integrations/erp/index.ts | Extends the lumos-ts ERPAdapter and modifies logging to use dynamic property access. |
| src/core/trpc.ts | Adds lumos-ts imports to support enhanced routing/context creation. |
| src/client.tsx | Introduces a browser process polyfill to support process-dependent code in the client. |
Files not reviewed (1)
- package.json: Language not supported
The import 'lumosCreateContext' is not used in this file; consider removing it to keep the code clean. Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Using 'this as any' to access 'name' and 'baseUrl' undermines type safety; consider exposing these properties via public getters in the base class to maintain robust type checking. Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
…iples:Separation of concerns with clear boundariesUse of adapters to interact with external servicesDependency Inversion through abstractionsClean interfaces between layersProper error handlingThe code is also ready for further extensions while maintaining backward compatibility.
No description provided.