Skip to content

fix(use-i18n): correct formatList and Context type #337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 23, 2021

Conversation

chambo-e
Copy link
Contributor

No description provided.

@chambo-e chambo-e requested review from a team, adriengibrat and DorianMaliszewski and removed request for a team August 20, 2021 21:24
@chambo-e chambo-e self-assigned this Aug 20, 2021
@chambo-e chambo-e force-pushed the fix/use-i18n_types branch from 126bcb1 to a6a5e9d Compare August 20, 2021 21:24
@codecov
Copy link

codecov bot commented Aug 20, 2021

Codecov Report

Merging #337 (a6a5e9d) into master (3a2204c) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##            master      #337   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        11           
  Lines          345       345           
  Branches        55        55           
=========================================
  Hits           345       345           
Impacted Files Coverage Δ
packages/use-i18n/src/usei18n.tsx 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a2204c...a6a5e9d. Read the comment docs.

@chambo-e chambo-e merged commit 2e97239 into master Aug 23, 2021
@chambo-e chambo-e deleted the fix/use-i18n_types branch August 23, 2021 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants