We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
for example, a model might have:
@BeforeSave() onBeforeSave() { }
Which gets called before modelThing.save().
modelThing.save()
Candidate decorators:
@BeforeSave()
@AfterSave()
@BeforeCreate()
@AfterCreate()
etc.
This will make it easier to make sure fields like updatedAt are automatically handled instead of having to worry each time you create or save a model.
updatedAt
These should be multiply applicable... i.e., you should be able to have as many @BeforeSave() on as many methods on a Model as you want.
These should also be async and they should allow the integrator to reject with the befores to stop the actual transaction from happening.
afterSave
afterCreate
The text was updated successfully, but these errors were encountered:
#166 BeforeSave
a3426a2
@BeforeSave
@BeforeCreate
4f71fc5
etsuo
No branches or pull requests
for example, a model might have:
Which gets called before
modelThing.save()
.Candidate decorators:
@BeforeSave()
@AfterSave()
@BeforeCreate()
@AfterCreate()
etc.
This will make it easier to make sure fields like
updatedAt
are automatically handled instead of having to worry each time you create or save a model.These should be multiply applicable... i.e., you should be able to have as many
@BeforeSave()
on as many methods on a Model as you want.These should also be async and they should allow the integrator to reject with the befores to stop the actual transaction from happening.
afterSave
,afterCreate
and other possible before/after decoratorsThe text was updated successfully, but these errors were encountered: