Open MoritzWeber0 opened 6 days ago
A Storybook preview is available for commit 9534e7b0e0b6569e7026ea67286e8c59eaa0d41a. ➡️ View Storybook ➡️ View Chromatic build ✅ Captured 27 snapshots. No changes detected.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.50%. Comparing base (
bc0ea05
) to head (d133ed0
). Report is 2 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Due to the stricter verification it's no longer possible to update the version of TeamForCapella servers. A version update of the TeamForCapella server would indicate that all linked repositories are migrated to the new Capella version automatically. This is not the usual update process. Instead, models are migrated one by one. This would be realized with the registration of another TeamForCapella server. Repositories are then slowly moved over. When the migration is finished, the old TeamForCapella server can be removed. The only valid use case I'm aware of that would require the modification of the version is that the user selected a wrong version during creation. In this case, the server has to removed and the integration has be created again.
The PR also fixes a bug that t4c models couldn't be moved to another T4C instance. The submit button of the T4C repository creation is now disabled when a request is running to avoid double-requests.
Is the last part of #1739. Resolves #1739.