20 Commits (35a330000ae4d1d7e1e6072a6859a45b5a92f415)

Author	SHA1	Message	Date
Gabriel Engel	35a330000a	removing @0.0.1 from rocketchat:ldap	10 years ago
Gabriel Engel	0455354552	clean up tap:i18n definitions on packages	10 years ago
Diego Sampaio	7cac1c4b2a	removed all console.logs from publishes and methods	10 years ago
Marcelo Schmidt	9c3870a84c	Removed debugging info on statistics. Closes issue #1552	10 years ago
Marcelo Schmidt	adad9cca89	New statistics: lastLogin, lastMessageSentAt, lastSeenSubscription, migration, version, branch and tag	10 years ago
Marcelo Schmidt	2da09c2caa	Fixed translations for rocketchat-statistics	10 years ago
Rodrigo Nascimento	aae6806522	Replace all Settings	10 years ago
Rodrigo Nascimento	9346f25984	Fix spelling	10 years ago
Rodrigo Nascimento	fa26d744ac	Replace all Statistics	10 years ago
Rodrigo Nascimento	b4024e641c	Replace "new Meteor.Collection" by @_initModel in models	10 years ago
Rodrigo Nascimento	e1597e617c	Remove comments	10 years ago
Rodrigo Nascimento	7cb07d2953	Replace all MapReducedStatistics	10 years ago
Rodrigo Nascimento	263c0d11e4	Replace all ChatMessage.find	10 years ago
Rodrigo Nascimento	2beff30027	Fix some mistakes and remove all references for ChatRoom	10 years ago
Rodrigo Nascimento	bfadb88b80	Replace all ChatRooms.find	10 years ago
Reid Wakida	c2e6e0fa2c	Create RocketChat authorization package that handles role and permission ... based authorization Leverages alanning:roles package to associate a user to a role. Uses alanning:roles optional "group" parameter to limit the role's scope to either the global level or room level. The global level is applicable to users that can perform administrative functions. The room level is applicable to users that can perform room specific administrative functions (like a moderator). A role can have zero or more permissions. Permissions and their association to roles are defined by this package Authorization checks are based on whether or not the user has a role or permission. The roles, permissions, and their association are statically defined at this time. Eventually, there should be an API to dynamically create a role and associate it to static permission(s). Old 'isAdmin' and '.admin is true' checks have been replaced with corresponding hasPermission authorization checks. Additionally, code that automatically assigned admin privileges are updated to assign 'admin' role instead. channel/direct message/private group code checks authorization to edit properties (e.g. title) and edit/delete messages (regardless of the system level allow edit/delete settings). - user with 'admin' role are authorized to do anything - room creator is assigned 'moderator' role that can edit the room and edit/delete messages - members can only edit/delete their own messages IF system wide settings permit them to. v19 migration will - add 'admin' role to users with admin:true property - add 'moderator' role scoped to room for room creators - add 'user' role to all users. There are known issues unrelated to the changes made - If a user with edit/delete message room permissions logs out then a user without edit/delete message room permissions logs in, then they will see edit/delete icons. The server will deny execution - edit/delete icons are not reactive Thus if the system level allow edit/delete message setting is toggled, the icons will not reflect it. The server will deny execution.	10 years ago
Marcelo Schmidt	6725283be3	Added meteor method getStatistics	10 years ago
Marcelo Schmidt	5954a7905f	Moved statistics to package	10 years ago
Marcelo Schmidt	14b2477d07	Initial development of statistics package	10 years ago