Content update

[devamitranjan]

Motivation

Fixed the failing of the status in the content in the cms.
Fixes #127

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (Storybook)
• I have added unit tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[devamitranjan]

@marrouchi Please review this and add hacktoberfest label in it. Thanks in advance.

[marrouchi]

Hello @devamitranjan

Thank you, I think we need to fix this differently.

Currently the controller path operation is using the ContentCreateDto

@CsrfCheck(true)
  @Patch('/:id')
  async updateOne(
    @Body() contentDto: **ContentCreateDto**,
    @Param('id') id: string,
  ): Promise<Content> {

We need to add another Dto for updates when we have two use cases :

• Either it's to update everyting : title, status, fields
• Just update the status attribute