Skip to content

Conversation

@skjnldsv
Copy link
Contributor

@skjnldsv skjnldsv commented Apr 7, 2023

@ChristophWurst do you know why @nextcloud/l10n is failing ?

@skjnldsv skjnldsv self-assigned this Apr 7, 2023
@codecov
Copy link

codecov bot commented Apr 7, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (97a2aab) 100.00% compared to head (29c0280) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #621   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          242       242           
  Branches        68        68           
=========================================
  Hits           242       242           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@susnux
Copy link
Contributor

susnux commented Apr 16, 2023

@skjnldsv I think because the @nextcloud/typings is not installed. It is just a dev dependency of l10n and no dependency of nextcloud-files.
I think either adding it is as a dev dependency of nextcloud-files or a (peer) dependency of l10n will fix this issue.

@skjnldsv skjnldsv requested a review from susnux April 16, 2023 14:36
@skjnldsv
Copy link
Contributor Author

@susnux well done! 🚀 🙏

@skjnldsv skjnldsv added type: bug 🐛 Something isn't working type: documentation 📖 Improvements or additions to documentation labels Apr 16, 2023
Copy link
Contributor

@susnux susnux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we should still add it is as a (peer) dependency to l10n but until then this is fine 👍

@skjnldsv
Copy link
Contributor Author

skjnldsv commented Apr 16, 2023

Probably we should still add it is as a (peer) dependency to l10n but until then this is fine +1

Hum, that's actually more correct. This doesn't belong here ? 🙈
ANyway, let's merge here and open a ticket in @nextcloud/l10n

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug 🐛 Something isn't working type: documentation 📖 Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants