@jaumard here is an example:
class _StripBearerProcessor implements FieldProcessor<String, String> {
const _StripBearerProcessor();
@override
String serialize(String value) => 'Bearer $value';
@override
String deserialize(String value) {
return value.substring(7);
}
}
@GenSerializer(
fields: {
'accessToken': Field(
processor: _StripBearerProcessor(),
),
},
)
class CustomerResponseSerializer extends Serializer<CustomerResponse>
with _$CustomerResponseSerializer {}
Examples seem to specify it as
const EnDecode(processor: _StripBearerProcessor) instead of Field(processor: ...) though, not sure which one is more correct: https://github.com/Jaguar-dart/jaguar_serializer/wiki/Basics
Thanks @rhalff ! I’ve updated the openapi generator with that to handle enums OpenAPITools/openapi-generator#3654 :)
Anyone is able to do multipart request with jaguar_retrofit or resty ? Look like it’s broken Jaguar-dart/client#62
But that wouldn't explain why it suddenly breaks, perhaps Uint8List was recently introduced somewhere within your own code?
what should it be serialized as though? In build_value there is a suggestion for base64 encoded in case of serializing to json: google/built_value.dart#194
you could solve that with a processor perhaps?
What’s the best practice for sharing a model between the client and server when using Jaguar Server and Serializers? Ideally I’d have a single class and I could generate the Bean file in a server only project, while the serializers are shared between the server and client. However, I found it necessary to introduce jaguar_orm within the shared code to annotate the model for the bean generation, but that caused builds to fail with the client (browser) side code.
And in my Db the values are good
I've got an issue where I have an entity called product groups, it has products. When I save the products and set their FK to catalog like so
@BelongsTo(ProductGroupEntityBean)
int productGroupId;if I save the products group with cascade the products aren't saved. If I save them both with an insert they're saved but when I get the productGroups I get no products in the collection. It's almost as though the relationships aren't being specified correctly. Is the above right? Is this the correct way to declare a relationship?
here's what the generated create function looks like:
Future<void> createTable({bool ifNotExists = false}) async {
final st = Sql.create(tableName, ifNotExists: ifNotExists);
st.addInt(id.name, primary: true, isNullable: false);
st.addStr(name.name, isNullable: false);
st.addInt(productCatalogId.name,
foreignTable: productCatalogEntityBean.tableName,
foreignCol: productCatalogEntityBean.id.name,
isNullable: false);
return adapter.createTable(st);