lupu60/nestjs-toolbox

The repository contains a suite of components and modules for Nest.js

{
  "name": "Bogdan Lupu",
  "skills":["typescript","express","nestjs","SQL"]
}

nestjs-toolbox's Issues

how to custom timestamp?

• I'm submitting a ...
  [ ] bug report
  [x] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary
  need reformat timestamp in log output

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

Which are updated or inserted

Is your feature request related to a problem? Please describe.
When performing upsert I would like to know which entity that updated or inserted.

Describe the solution you'd like
return the status (inserted or updated)

TypeOrmUpsert return issue

return Promise<T[]|T>; on TypeOrmUpsert

Limit max log string length

Is your feature request related to a problem? Please describe.
Is there a way to simply limit the size of the logged message ?

Describe the solution you'd like
Providing an option like maxLength, that would handle string slicing.

Doesn't honor the 'color' property on the formatterOptions

Setting the 'color' property to false on the formatterOptions has no effect. BunyanLoggerService should use the property, instead its hard coded to color the error and warn messages with red and yello

BunyanLogger extending built in Logger

Looking to use the BunyanLogger in this context: https://docs.nestjs.com/techniques/logger#injecting-a-custom-logger

Where I can do setContext, which seems to be provided by the built in Logger. Could the BunyanLogger extend that to provide this, or is it more involved?

Looks like BunyanLogger takes a context as the second param to log, but in a class scenario it's tedious to have to set that every time in the class.

conflict key use index.

Issue with structured logging - Seq

Describe the bug
When using Seq logging (I am using the package bunyan-seq to create a custom stream) The string interpolation / variable substitution does not work

To Reproduce
Steps to reproduce the behavior:

1. Include bunyan-seq package to your project along with @nest-toolbox/bunyan-logger
2. Setup the logging service as mentioned below in the main.ts
3. In the controller's create an instance of Logger from @nestjs/common
4. call the logger methods as described below and see the results

Expected behavior
When logging with the following statement:
this.logger.warn('{user} tried access the {service} service with an expired key!',{ user: 'E73882', service: 'PurchaseOrder'});
the output in the log should be
E73882 tried access the PurchaseOrder service with an expired key!

Screenshots
What happens is:

Additional context
Here is my main.ts:

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

const seq = require('bunyan-seq');

async function bootstrap() {
  const app = await NestFactory.create(AppModule,{
    bufferLogs: true,
  });

  app.useLogger(new BunyanLoggerService({      
        projectId: 'NestJS-Microservice',
        formatterOptions: {
          outputMode: 'json',
        },
        customStreams:[seq.createStream({serverUrl: 'http://localhost:5341', apiKey: '123456789'})]  ,
        extraFields: {
          app: 'extra-field-app',
          sample: 'extra-field-sample'
        }    
    }));

  await app.listen(3000);
}
bootstrap();`


In the controller in just create a Logger instance as follows and uses it:


`private readonly logger = new Logger('AppController');`

Examples:
 `this.logger.warn('English hello {lang}',{ lang: 'en' });    `

Not updating updatedAt

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Create entity with updatedAt column using TypeOrm:

@UpdateDateColumn()
public updatedAt!: Date;

1. Do an upsert with one element await TypeOrmUpsert.upsert(English, [{ path: 'foo', phrase: 'hi'}], 'path');

Expected behavior
The "updatedAt" column should update.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS
• Browser: All (Firefox latest, Chrome latest, Safari latest)
• Version: "@nest-toolbox/typeorm-upsert": "^1.4.2",

Smartphone (please complete the following information):
not applicable

Additional context
not applicable

Support node 12

Right now only node 14 is supported. Can Node 12 be used in addition?

yarn
...
error @nest-toolbox/[email protected]: The engine "node" is incompatible with this module. Expected version "14". Got "12.22.3"