The integration of the TES components into Krini has become a smoother process. Here are the key steps involved:
Packaging & Deployment: Successfully packaged and deploy the TES component library as a pre-release version on NPM. This ensures that the components are readily available for integration.
Configuration Update: To complete the integration, remove the old Krini configuration and replaced it with the new TES components. This update aligns Krini with the latest component library, enhancing its functionality and user experience.
Extended Functionality: In addition to the core integration, we have an extended goal. We aim to replace the LS AAI login button by leveraging the new component. This allows us to abstract and centralize common logic, making our codebase more maintainable and efficient. You can track the progress of this goal in the pending pull request here: GitHub PR #67.
These steps signify a significant improvement in the ease of integrating TES components into Krini.
The integration of the TES components into Krini has become a smoother process. Here are the key steps involved:
Packaging & Deployment: Successfully packaged and deploy the TES component library as a pre-release version on NPM. This ensures that the components are readily available for integration.
Configuration Update: To complete the integration, remove the old Krini configuration and replaced it with the new TES components. This update aligns Krini with the latest component library, enhancing its functionality and user experience.
Extended Functionality: In addition to the core integration, we have an extended goal. We aim to replace the LS AAI login button by leveraging the new component. This allows us to abstract and centralize common logic, making our codebase more maintainable and efficient. You can track the progress of this goal in the pending pull request here: GitHub PR #67.
These steps signify a significant improvement in the ease of integrating TES components into Krini.