Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't use a model for each thing #21

Open
alecho opened this issue Sep 17, 2015 · 1 comment
Open

Don't use a model for each thing #21

alecho opened this issue Sep 17, 2015 · 1 comment
Assignees
@alecho
Labels
RFC

Comments

@alecho
Copy link
Member

alecho commented Sep 17, 2015

No description provided.

@alecho alecho self-assigned this Sep 17, 2015
@alecho alecho mentioned this issue Sep 17, 2015
Closed
@alecho
Copy link
Member Author

alecho commented Sep 17, 2015

After the meetup tonight I had some time to think. I'm flipping my opinion on this one. I think it does make more sense for things to have and belong to many attributes. What made me change my mind was thinking about how to implement thing creation in a consuming app and the amount of value that adds. It seems like a good idea to be able to create things as needed.

I think if we are going to allow consumers to create things and related attributes then we need to have an authorization system in place so that only authorized users can create things to track.

@alecho alecho added the RFC label Sep 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alecho alecho

Labels
RFC
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alecho