Anytime Mortar updates a property on an object for internal use, the key should obscure to not conflict with user data

MortarJS / Mortar-JS

A React-powered framework that provides building blocks to craft and customize powerful data management tools for the web.

MIT License

101 stars 3 forks source link

Anytime Mortar updates a property on an object for internal use, the key should obscure to not conflict with user data #11

Open Kyle-Mendes opened 8 years ago

Kyle-Mendes commented 8 years ago

For example: https://github.com/fuzz-productions/Mortar-JS/blob/dev/lib/components/visualization/tables/Row.js#L339-L342

Here, I'm adding a selected key to the data being passed into the table data. This should ideally be something like mortar-table-selected or something. If the user already has a selected property on their data, we'd be overwriting that value, and probably in a way they don't want / intend.