|
@@ -1,6 +1,6 @@
|
|
pragma solidity ^0.4.23;
|
|
pragma solidity ^0.4.23;
|
|
|
|
|
|
-import "./RBAC.sol";
|
|
|
|
|
|
+import "../ownership/rbac/RBAC.sol";
|
|
|
|
|
|
|
|
|
|
/**
|
|
/**
|
|
@@ -8,6 +8,13 @@ import "./RBAC.sol";
|
|
* @author Matt Condon (@Shrugs)
|
|
* @author Matt Condon (@Shrugs)
|
|
* @dev It's recommended that you define constants in the contract,
|
|
* @dev It's recommended that you define constants in the contract,
|
|
* @dev like ROLE_ADMIN below, to avoid typos.
|
|
* @dev like ROLE_ADMIN below, to avoid typos.
|
|
|
|
+ * @dev
|
|
|
|
+ * @dev NOTE: RBACWithAdmin is probably too expansive and powerful for your
|
|
|
|
+ * @dev application; an admin is actually able to change any address to any role
|
|
|
|
+ * @dev which is a very large API surface. It's recommended that you follow a strategy
|
|
|
|
+ * @dev of strictly defining the abilities of your roles
|
|
|
|
+ * @dev and the API-surface of your contract.
|
|
|
|
+ * @dev This is just an example for example's sake.
|
|
*/
|
|
*/
|
|
contract RBACWithAdmin is RBAC {
|
|
contract RBACWithAdmin is RBAC {
|
|
/**
|
|
/**
|