docs: mention id field in 1-abstract-dto.rst

[sobolevn]

It caught my attention that it was never explained: why do we have an extra id field in the response. Since this part is dedicated to explaining how request / response fields are marked, I think that it is important to mention that id is special:

I had to grep what .my_lib is and how class _Base(CommonTableAttributes, UUIDPrimaryKey, DeclarativeBase): is constructed. Only finding UUIDPrimaryKey and its id: Mapped[UUID] = mapped_column(default=uuid4, primary_key=True) has anwsered my question :)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3803

[provinzkraut]

I'm not really sure "special" is the right wording here, since it's simply an inherited attribute. It only happens to be the only one that's inherited from the base class, but there's nothing special about the id attribute itself

[sobolevn]

@provinzkraut can we say that "id is readonly because it is a primary key"?

[provinzkraut]

@provinzkraut can we say that "id is readonly because it is a primary key"?

I think it should say something like "we mark id read only since it represents a primary key", to emphasize that this isn't done automagically, and could apply to other arbitrary fields as well