تحويل الكائنات إلى JSON

Turning a model object into plain JSON-ready data is called dumping. The schema reads your object and emits a clean dict.

Pass your object to the schema's dump method. It returns a dictionary containing only the fields you declared, properly typed.

The output of dump is an ordinary Python dict, not JSON text yet. That dict is exactly what jsonify happily turns into a response.

Hand the dumped dict to Flask's jsonify to get a real response with the right content type and proper formatting.

Have a list of objects? Create the schema with many=True and dump returns a list of dicts in one tidy call.

You can also pass many=True straight to dump on an existing instance, so one schema serves both single and list endpoints.

Declare a Nested field and dump walks into related objects too. One call serializes a user and all of their posts together.

Because you used a DateTime field, dump renders it as an ISO string with no extra work. Consistent timestamps come for free.

Dump ignores anything not in the schema. Internal attributes like password_hash simply never show up, so your output stays safe.

Remember that dump trusts your objects and does no validation. It is purely about output; checking input is the job of load.

Put it together: query the model, dump it, jsonify it, return it. That short pipeline replaces all those fragile hand-built dicts.

You need to serialize a list of user objects.

Use dump to turn objects into JSON-ready dicts, add many=True for lists, and let Nested fields handle relations. Then jsonify and return.