Skip to content

pg-promise refactoring #4401

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 2 commits into from
Nov 30, 2017
Merged

pg-promise refactoring #4401

merged 2 commits into from
Nov 30, 2017

Conversation

vitaly-t
Copy link
Contributor

initial refactoring of pg-promise code.

initial refactoring of `pg-promise` code.
@vitaly-t
Copy link
Contributor Author

The issue on Travis CI is unrelated to the change.

@flovilmart
Copy link
Contributor

If you rebase on master this should be good!

Copy link
Contributor

@flovilmart flovilmart left a comment

Choose a reason for hiding this comment

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

What’s the relationale behind the dash-cased tx names vs camelCase? Just conventions?

@vitaly-t
Copy link
Contributor Author

@flovilmart yes, just conventions. Also, in line with the use of pg-monitor, which I believe you guys are not using, though it is very useful, to be able to see exactly what is going on. 😉

@codecov
Copy link

codecov bot commented Nov 30, 2017

Codecov Report

Merging #4401 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4401      +/-   ##
==========================================
- Coverage   92.66%   92.64%   -0.03%     
==========================================
  Files         118      118              
  Lines        8348     8346       -2     
==========================================
- Hits         7736     7732       -4     
- Misses        612      614       +2
Impacted Files Coverage Δ
...dapters/Storage/Postgres/PostgresStorageAdapter.js 96.83% <100%> (-0.01%) ⬇️
src/Adapters/Auth/meetup.js 84.21% <0%> (-5.27%) ⬇️
src/RestWrite.js 93.1% <0%> (-0.19%) ⬇️

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 9eed81e...06606fb. Read the comment docs.

@vitaly-t vitaly-t merged commit 9d1d851 into master Nov 30, 2017
@vitaly-t vitaly-t deleted the vitaly-t-patch-2 branch November 30, 2017 01:30
@vitaly-t
Copy link
Contributor Author

@flovilmart I should have just used ES6 yield for now, which works the same, will do in another PR ;) Those will be directly convertible into await/async ;)

@flovilmart
Copy link
Contributor

Let’s try not to have Babel regenerator runtime as we’ve had performance problems with it in the past, that’s why I aim to maintain the minimum amount of transpilation and move forward with LTS. Now we’re targeting 6.11. And we could /should probably target current LTS. What do you think?

@vitaly-t
Copy link
Contributor Author

vitaly-t commented Nov 30, 2017

@flovilmart That's absolutely not what I suggested. ES6 generators are supported since Node 4 😉 Also, I never use Babel for anything, not a fan of its over-the-head project configurations 😄

@flovilmart
Copy link
Contributor

Perfect then! Wasn’t sure since when they were available .)

flovilmart pushed a commit that referenced this pull request Dec 29, 2017
initial refactoring of `pg-promise` code.
UnderratedDev pushed a commit to UnderratedDev/parse-server that referenced this pull request Mar 21, 2020
initial refactoring of `pg-promise` code.
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.

2 participants