feat: 'suppressReadonlyModifier' override option introduced

[mironbalcerzak]

Status

READY

Fixes #1348

Description

suppressReadonlyModifier override option to stop usage of readonly modifier in models

Related PRs

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

[melloware]

Is this related to any open tickets?

[mironbalcerzak]

@melloware - found an issue in a generated code against my schema.
Someone is already addressing it here: #1352.

Bigger picture, usage of "readonly" in code is opinionated - this gives user a freedom to choose.

[melloware]

OK I merged that other PR. It looks like you have failing tests?

[melloware]

cc @ezequiel

[mironbalcerzak]

@melloware - should be alright now

[cliveportman]

Was this ever released? I'm on 6.30.2 but I'm getting suppressReadonlyModifier does not exist when trying to add to the output config. And I've got readonly throughout my generated types.

I'm assuming that because it's in the docs without a version flag, then it's meant to be in?

[melloware]

This was in version 6.29.0 . @mironbalcerzak can you clarify?

[cliveportman]

@melloware Got it. It needs to be part of the override object, it's the docs that are the issue. I'll create an issue and PR off that for correcting the docs.

[mironbalcerzak]

@melloware - correct, it was released in 6.29.0.
@cliveportman - correct, it's a part of override, like this:

output: {
    override: {
        suppressReadonlyModifier: true
    }
}