profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bashleigh/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Ashleigh Simonelli bashleigh Ruddr Southend ashleighsimonelli.co.uk Code Specialist | SaaS builder | MVP specialist | Contractor | Consultant | rockstar

bashleigh/nestjs-blog 152

Blog example made with nestJS

bashleigh/another-portfolio 10

My portfolio at https://ashleighsimonelli.co.uk

bashleigh/GPIO 6

GPIO pin environment manager

bashleigh/nestjs-config-v2-prototype 6

An example/prototype of v2 for nestjs-config

bashleigh/areyouinfordinner-api 4

API for Are You In For Dinner :fork_and_knife:

bashleigh/areyouinfordinner-app 2

App for communicating with the are you in for dinner API :fork_and_knife:

bashleigh/communication-experiment 2

An experiment of different methods of communication using nestjs

bashleigh/nest 2

A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications on top of TypeScript & JavaScript (ES6, ES7, ES8) 🚀

bashleigh/awesome-nestjs 1

😏 Curated list of NestJS

startedcorpnewt/SSDTTime

started time in 19 minutes

issue commentnestjsx/nestjs-typeorm-paginate

Wrong page counting

Ok so from your comments it's not an issue with the pagination package, it's an issue with typeorm not allowing you to perform a count query with a group by. According to this issue https://github.com/typeorm/typeorm/issues/544 this is a work around. However I cannot implement this into the pagination package because I feel the package would no longer be agnostic. Therefore I'm not sure what to suggest. The only possible solution to 'resolve' your issue without making the package too selective, is to add a optional feature for a custom count query. What do you think about that?

Btw, https://github.com/typeorm/typeorm/issues/544 does not see to be the issue I am facing.

The count query is simply wrong as it omits the group by sql clause despite it being used... can you double confirm that this count query is implemented in typeorm vs typeorm-paginate?

ForeshadowRU

comment created time in 42 minutes

issue commentnestjsx/nestjs-typeorm-paginate

Wrong page counting

Thanks,

Strangely that typeorm returns the count, which is used for pagination, and not the paginate module, which is used for... pagination! Anyways...

Anything that helps is appreciated, unsure what you mean by "optional feature". Can you please elaborate?

ForeshadowRU

comment created time in an hour

startedisaachinman/next-i18next

started time in 3 hours

startedTryGhost/Ghost

started time in 4 hours

startedvue-leaflet/vue-leaflet

started time in 4 hours

startedUrigo/graphql-scalars

started time in 4 hours

issue commentnestjsx/nestjs-typeorm-paginate

Wrong page counting

have you tried using an array in groupBy instead? groupBy([])?

No, should i have done that?

So you mean groupBy(['run_id', 'market', 'area']) instead of .groupBy('run_id') .addGroupBy('market') .addGroupBy('area') ?

Yeah, so .groupBy() is only expecting a string, not an array of strings, see "Argument of type 'string[]' is not assignable to parameter of type 'string'." I wonder why you'd suggest that?

It's a clear bug in the pagination module. See the printed queries, from which one can see the group by clause in the main query, and missing group by clause in the count query.

query: SELECT COUNT(1) AS "cnt" FROM "mv_..." "t" WHERE run_subreddit IN ($1, $2, $3, $4, $5, $6, $7, $8) AND sub_created_utc_tmstmp >= NOW() - INTERVAL '24 hours' HAVING SUM(total_hype_level_24h) <> 0 -- PARAMETERS: ["wallstreetbets","pennystocks","RobinHoodPennyStocks","Daytrading","StockMarket","stocks","trakstocks","SPACs"]

query: SELECT run_id, market_symbol, ticker_symbol, SUM(num_posts) num_posts, SUM(num_distinct_authors) num_distinct_authors, SUM(num_upvotes) num_upvotes, SUM(num_comments) num_comments, SUM(total_hype_level_24h) total_hype_level, ROUND( SUM(current_hype_level_24h)/NULLIF(SUM(total_hype_level_24h), 0) * 100) change_hype_level, RANK() OVER (ORDER BY SUM(total_hype_level_24h) DESC) rank FROM "mv_..." "t" WHERE run_subreddit IN ($1, $2, $3, $4, $5, $6, $7, $8) AND sub_created_utc_tmstmp >= NOW() - INTERVAL '24 hours' GROUP BY run_id, market_symbol, ticker_symbol HAVING SUM(total_hype_level_24h) <> 0 ORDER BY rank ASC LIMIT 25 -- PARAMETERS: ["wallstreetbets","pennystocks","RobinHoodPennyStocks","Daytrading","StockMarket","stocks","trakstocks","SPACs"]

Can you please open the bug to reflect the correct status? And, until fixed, can you possibly suggest any workarounds?

ForeshadowRU

comment created time in 4 hours

issue commentnestjsx/nestjs-typeorm-paginate

Wrong page counting

have you tried using an array in groupBy instead? groupBy([])?

No, should i have done that?

So you mean groupBy(['run_id', 'market', 'area']) instead of .groupBy('run_id') .addGroupBy('market') .addGroupBy('area') ?

ForeshadowRU

comment created time in 4 hours

startedtj/git-extras

started time in 4 hours

issue commentnestjsx/nestjs-typeorm-paginate

Wrong page counting

Was typeorm adding both group bys to both queries? You don't have any joins so I'm guessing it's to do with the double group by? If so this is definately an issue with typeorm and not the paginate package so I'm not sure what else I can suggest or fix to help you without suggesting a specific fix for this specific query

thx for the reply - that's the issue - typeorm DOES NOT implement the groupBy clause to the internal count query, despite the fact that groupBy is used in the main query, resulting in a wrong count (higher no. of records than grouped by); there are no joins. See here https://github.com/nestjsx/nestjs-typeorm-paginate/issues/6#issuecomment-779481460

ForeshadowRU

comment created time in 9 hours

startedformstjs/formst

started time in 9 hours

startedbrandonbloom/uni

started time in 10 hours

startedplausible/analytics

started time in 13 hours

delete branch nestjsx/nestjs-braintree

delete branch : dependabot/npm_and_yarn/types/node-14.14.31

delete time in 13 hours

PR closed nestjsx/nestjs-braintree

Bump @types/node from 12.7.9 to 14.14.31 dependencies

Bumps @types/node from 12.7.9 to 14.14.31. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+4 -4

1 comment

2 changed files

dependabot-preview[bot]

pr closed time in 13 hours

pull request commentnestjsx/nestjs-braintree

Bump @types/node from 12.7.9 to 14.14.31

Superseded by #150.

dependabot-preview[bot]

comment created time in 13 hours

PR opened nestjsx/nestjs-braintree

Bump @types/node from 12.7.9 to 14.14.32

Bumps @types/node from 12.7.9 to 14.14.32. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+4 -4

0 comment

2 changed files

pr created time in 13 hours

PR opened nestjsx/nestjs-typeorm-paginate

chore(deps-dev): bump @types/node from 14.14.31 to 14.14.32

Bumps @types/node from 14.14.31 to 14.14.32. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+6 -6

0 comment

2 changed files

pr created time in 13 hours

PR opened nestjsx/nestjs-amqp

chore(deps-dev): bump @types/node from 14.14.31 to 14.14.32

Bumps @types/node from 14.14.31 to 14.14.32. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+3 -3

0 comment

1 changed file

pr created time in 14 hours

create barnchnestjsx/nestjs-amqp

branch : dependabot/npm_and_yarn/types/node-14.14.32

created branch time in 14 hours

startedsandhillsdevelopment/claws

started time in 14 hours

startedflanksource/template-operator

started time in 15 hours

created repositorynxpm/stack-v4160

created time in 19 hours

created repositorynxpm/nxpm-docs

created time in a day

startedaelbore/vite-angular-experiment

started time in a day

issue commentnestjsx/nestjs-config

Unable to app.get(ConfigService) in main.ts with node lts (12.16.0)

I had the same problem and solved it by first importing the ConfigModule in app.module.ts like mentioned in the documentation.

After that, I could use it in the main.ts without problems (example main.ts):

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import { Logger } from '@nestjs/common';
import { ConfigService } from '@nestjs/config';
import { NestExpressApplication } from '@nestjs/platform-express';

async function bootstrap() {
  const logger = new Logger('Bootstrapper');

  const app = await NestFactory.create<NestExpressApplication>(AppModule);
  const config = app.get<ConfigService>(ConfigService);

  const port = config.get('API_PORT');
  await app.listen(Number(port));

  logger.log(`App listening on port ${port}`);
}
bootstrap();
arvinsingla

comment created time in a day

startednanojsx/nano

started time in a day