Closed joffrey-bion closed 7 years ago
Type exploration, as of now, is based on fields instead of actual serializable properties. Without a more flexible approach, we end up with problems like: https://github.com/joffrey-bion/livedoc/issues/10 https://github.com/fabiomaffioletti/jsondoc/issues/153 https://github.com/fabiomaffioletti/jsondoc/issues/159 https://github.com/fabiomaffioletti/jsondoc/issues/199 https://github.com/fabiomaffioletti/jsondoc/issues/215 https://github.com/fabiomaffioletti/jsondoc/issues/207 https://github.com/fabiomaffioletti/jsondoc/issues/230
We want to be able to customize the way we list properties of a class, in particular how we name them and which ones to ignore.
Type exploration, as of now, is based on fields instead of actual serializable properties. Without a more flexible approach, we end up with problems like: https://github.com/joffrey-bion/livedoc/issues/10 https://github.com/fabiomaffioletti/jsondoc/issues/153 https://github.com/fabiomaffioletti/jsondoc/issues/159 https://github.com/fabiomaffioletti/jsondoc/issues/199 https://github.com/fabiomaffioletti/jsondoc/issues/215 https://github.com/fabiomaffioletti/jsondoc/issues/207 https://github.com/fabiomaffioletti/jsondoc/issues/230
We want to be able to customize the way we list properties of a class, in particular how we name them and which ones to ignore.