how to limit attributes on resource? about epilogue

[mbroadst]

We don't currently support explicitly including/excluding certain attributes during resource definition, but it's not a bad idea. If you don't want to do any work on the module itself the way to go today is to remove the attributes you don't want to expose with a milestone.

If, on the other hand, you're interested in helping build out the feature: we already work with options.attributes here in order to remove duplicate returned data when using includes. You could perhaps provide a top level attributes and/or excludeAttributes option to epilogue.resource which could further fine-tune that parameter before sending it to model.find below. This would be a pretty quick fix if you were so inclined

[philotas]

Ok. I am quite new to node, express and sequelize etc, but I gave it a shot:

philotas@5667765

It now works as I wished and currently it only supports attributes but not excludeAttributes.

I also did no write any test but the existing tests ran without errors.

If you have any suggestions for improvements, feel free to let me know. Thanks!

[mbroadst]

@philotas thanks for the work! I'll pull it in presently and write a test or two for it. Are you sure that excludeAttributes wouldn't suite your purposes better? That way you wouldn't have to manually write out each attribute, just the ones you don't want

[mbroadst]

@philotas merged in e30fbfd, you were attributed in the previous commit. I went with excludeAttributes as that seems to be the primary use case, however resource.attributes still exists and can be modified directly

[philotas]

thanks!