trustedshops-public / connect-app-demo Goto Github PK

Hi @Mhera17 ,

our aim in this repository is to create a demo app, which includes our connector layer to enable external developers an easy and independent engineering.
Therefore we want to include this repo in our public github organization.

To be fit for it, we need to tackle a checklist of our opensource guild.

One task is: Integrate DCO App into your project

Do you have experience with DCO Check? Could you implement this in the repo?

Greetings

Hi @Mhera17 ,

Aleks and Said started this repo with different branches. Now its time to get this together and go on working in the main branch. Could you go through the branches and merge everything together that the main branch is working fine?

If the demo app is not understandable at first sight, here is a first draft of the docu.

https://developers.etrusted.com/solutions/newgen-sdk/introduction.html

Please come to us when you have questions.

Greetings

After clicking the button Close connector, cannot open it again when clicking Open connector button.

Steps to reproduce:

1. checkout branch "initialization"
2. run the app
3. click on button Open connector
4. click button Close connector

Description

New functionality of connector / eventslib should be reflected in Demo-App as well:

• add switch to v2 at informationOfSystem
• add reasonable test data for available order statuses
• add reasonable test data for set order statuses
• add storage of selected order status to local storage
• add console output for new events

References

No response

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency vite to v5.0.12 [security]
• chore(deps): update node.js to v21.6.2
• chore(deps): update npm (@types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, @vitest/ui, autoprefixer, axios, eslint, eslint-plugin-jest, eslint-plugin-prettier, lint-staged, postcss, preact, prettier, react-hook-form, tailwindcss, vitest, zustand)
• chore(deps): update dependency happy-dom to v13
• chore(deps): update dependency husky to v9
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Description

Hi @Mhera17 ,

in the past you changed the integrated build of the connector and eventslib.
#22

With our repositories https://github.com/trustedshops-public/connect-app-eventslib and https://github.com/trustedshops-public/connect-app-connector now publicly available, we changed our deployment to release packages with versioning.

We want to adapt this in our NewGen Demo App.

Aim:
1a. Integrate the build of eventslib and connector directly from the release package
1b. we need to find a method to identify the version of build implemented in demo app (Do you have any idea where to put this information?)
2. Create a release package of demo app (version 1.0.0)

Keep in mind:
In future we want/you need to manually create a new version of the demo app, when there are breaking changes in Connector Layer or Eventslib. External developer need to comprehend the used build and changes

Greetings

References

No response

Hi @Mhera17 ,

Status Quo
Connector and Eventslib build is integrated via our AWS Deployment in the Demo App. (I think it is this part of the code) Our long term goal is to have a local, versioned integration of the connector and eventslib in the demo app.

Pain Point
We want to send the demo app to two external developers which are in the loop to build two plugins for us. This development should not be based on our AWS deployment. Therefore we want to change the used build in our demo app from AWS deployment to a local integrated build of connector and eventslib.

ToDo
Could you investigate, what needs to be changed and how this could be implemented? Aleks created public file with the connector.js and the eventslib.js , but we think it isn used at the moment. Furthermore the scripts we will integrate should be updated and be the status quo of current main branch of spike and eventslib repo.

Please ask if something is not understandable or wrong from my side.

Greetings