[
https://issues.apache.org/jira/browse/AIRAVATA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766572#comment-17766572
]
Marcus Christie commented on AIRAVATA-3699:
-------------------------------------------
Hi [~jcrantford], I wanted to follow up on a conversation we had about Web
Component testing.
I unfortunately didn't have time to investigate how to better test Vue.js Web
Components. However, I did a little research to see if any of our gateways are
actively using Web Component custom user interfaces, and none are. So I think
you can just deprioritize migrating the Web Components for now. If the code is
causing you can issue you can remove the "build:wc" steps from the package.json
https://github.com/apache/airavata-django-portal/blob/master/django_airavata/apps/workspace/package.json#L17-L18
We can create a follow on issue to investigate converting the Web Components to
new Vue 3 style.
> Upgrade Django Portal frontend to use Vue 3
> -------------------------------------------
>
> Key: AIRAVATA-3699
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3699
> Project: Airavata
> Issue Type: Improvement
> Components: Django Portal
> Reporter: Marcus Christie
> Priority: Major
>
> The Django Portal Vue.js code currently uses Vue 2.6. Vue 2 is reaching it's
> end-of-life (EOL) on Dec 31, 2023 (https://v2.vuejs.org/lts/). It would be
> good to upgrade to Vue 3 before that happens.
> Vue 3 Migration Guide:
> https://v3-migration.vuejs.org/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
