Skip to content
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

feat(mongoose): upgraded mongoose and rename context #141

Merged
1 commit merged into from
Oct 5, 2022

Conversation

ghost
Copy link

@ghost ghost commented Oct 5, 2022

upgraded mongoose dependency from v5 to v6 and renamed context to davinciContext to avoid type collisions with mongoose context

…d context to davinciContext to avoid type collisions with mongoose context
@ghost ghost requested a review from pierissimo October 5, 2022 10:08
@ghost ghost self-assigned this Oct 5, 2022
@codecov
Copy link

codecov bot commented Oct 5, 2022

Codecov Report

Merging #141 (4c91957) into master (9fe82c0) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   74.72%   74.72%           
=======================================
  Files          28       28           
  Lines        1183     1183           
  Branches      285      285           
=======================================
  Hits          884      884           
  Misses        199      199           
  Partials      100      100           
Flag Coverage Δ
core 79.90% <ø> (ø)
graphql 72.05% <ø> (ø)
mongoose 61.61% <ø> (ø)
reflector 82.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@ghost ghost merged commit 1c39596 into master Oct 5, 2022
@ghost ghost deleted the feat/major-release-mongoose-6-context-rename branch October 5, 2022 10:15
This pull request was closed.
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.

1 participant