Strict model: Add new field at runtime #224

New issue

Closed

opened 2021-03-09 02:39:18 +00:00 by jamie · 3 comments

jamie commented

2021-03-09 02:39:18 +00:00

(Migrated from git.hazaar.io)

I have an instance where I want to add a new field at runtime. Normally this isn't allowed as it goes against the principles of strict models in the the strict part is that it's supposed to restrict what can be added to a model and the data type. To do this, we need to define the field and it's type.

However it should be OK to add a new field definition at runtime. The case I'm thinking of is using DBI to get a row from a table using Hazaar\Table::findOneRow() which returns a Hazaar\DBI\Row object which itself extends Hazaar\Model\Strict and automatically defines all the fields in the model using the returned columns, including their type and any custom features/functions for those types that are provided by the row class. In a REST API, I want to return this row as is, allowing the Row class to do it's thing, but I want to add a field to the returned object (in this case, a URL).

I have an instance where I want to add a new field at runtime. Normally this isn't allowed as it goes against the principles of strict models in the the _strict_ part is that it's supposed to restrict what can be added to a model and the data type. To do this, we need to define the field and it's type. However it should be OK to add a new field definition at runtime. The case I'm thinking of is using **DBI** to get a row from a table using `Hazaar\Table::findOneRow()` which returns a `Hazaar\DBI\Row` object which itself extends `Hazaar\Model\Strict` and automatically defines all the fields in the model using the returned columns, including their type and any custom features/functions for those types that are provided by the row class. In a REST API, I want to return this row as is, allowing the Row class to do it's thing, but I want to add a field to the returned object (in this case, a URL).

jamie commented

2021-03-09 02:39:32 +00:00

(Migrated from git.hazaar.io)

created merge request !114 to address this issue