Skip to content

Conversation

@Astaldos
Copy link
Contributor

@Astaldos Astaldos commented Apr 9, 2025

No description provided.

return value?.toString();
} else if (field.name === '_id' && !field.fillOnCreate) {
// if "_id" was created by mongo it will be ObjectId
return value?.toString();
Copy link
Contributor

@ivictbor ivictbor Apr 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Astaldos I am a little bit afraid of case if user returns bson object from fillOnCreate.

Maybe it is better to check it like if type of value is object then do .toString(), is it safe or you see any potential issues with it?

return Decimal128.fromString(value?.toString());
} else if (field.name === '_id' && !field.fillOnCreate) {
// if "_id" was created by mongo it supposed to be saved as ObjectId
return ObjectId.createFromHexString(value);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, we can check if value is type of string or number or null or undefined, then wrap it in bson Object id, otherwise pass "as is"

return !!value;
} else if (field.type == AdminForthDataTypes.DECIMAL) {
return value?.toString();
} else if (field.name === '_id' && !field.fillOnCreate) {
Copy link
Contributor

@ivictbor ivictbor Apr 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Astaldos will it brake something if we will remove && !field.fillOnCreate? I mean for the case if user returns object id in fillOnCreate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants