LDAP search should be configurable – not all companies store their primary employee information in a field called mail, which is currently hardcoded at lib/model/db/company.js

For DELETES, in this line https://github.com/tommybananas/finale/blob/master/lib/Controllers/delete.js#L23 the instance is removed from the context, which greatly limits what can be done in hooks after write.

A temp solution I have is backing up the instance in another hook, but this seems to be limiting. Sequelize destroy hooks still retain the instance in memory so that hooks can use informat

The versions I'm using:

    "sequelize": "^5.18.4",
    "sequelize-cli": "^5.5.1",
    "sequelize-paper-trail": "^3.0.1",

For some reason, when a new Revision record is created, it is missing these columns:

 id | model | document | operation | revision | document_id |         createdAt          |         updatedAt
----+-------+----------+-----------+----------+----------

Hello,

I was following yours great tutorial but I tried to set up my project using Sequelize v5, instead of v4, however, I got many errors regarding types incompatibility. Please check my code below.

import * as Sequelize from 'sequelize';

export interface UserAttributes {
    id?: number;
    name: string;
    createdAt?: Da

• Items should have optional "price" field
• Field already exists on the Item object
• Value will need to be passed to backend w/ payload

Hi Guys, I'm using this package to make full text searches in my current system. I've followed the steps on how to implement the materialized views suggested on the documentation with no luck. I'm getting the following error

TypeError: Cannot read property 'field' of undefined
    at Object.keys.forEach.key (~/proj/node_modules/pg-search-sequelize/lib/queryGenerator.js:100:59)
    at Arra

Right now the result of sequelize-auto-import is an object that will have its properties equal to the model name of the meta object that we pass to each model, but practically the dev can choose to not use these values an put other values for the model name and schema so we must extract these values from the sequelize model instead.

What's this issue about?

If a user doesn't own a park, they should not be able to create spots or carspots on that park

Hi Ahmer!
Thank for the excellent article https://vivacitylabs.com/setup-typescript-sequelize/. It was super useful in my TS migration.

I have a comment on the article and this is the only way I found to reach you. :-)

In CommentAttributes, you add the relation attribute as post?: PostAttributes | PostAttributes['id'];.

I don't think the PostAttributes['id'] part is right as Seque

• hostname/Player/:id 처럼 라우터를 설정할 경우, 새로고침으로 진입할 수 없음
• react-router-dom 관련 문제임
• 해결책은 찾음
• 해결책
• build/index.html에서 script태그의 src="bundle.js를 src="/bundle.js"로 고치면 해결

문제

• 빌드할 때마다 수동으로 고쳐줘야 하나?
• 해결책1. 스크립트 파일을 하나 짜서, npm run build 할 때마다 같이 실행되도록 한다.