From 538120f7d1425e026220211857658a775c958577 Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Wed, 11 Mar 2015 13:47:55 +0100 Subject: [PATCH] fix(mbuild): scope -> add_scope This is not only more precisely saying what it does, but also doesn't clash with scope parameters on resources ;) (happened in dfareporting) --- src/mako/lib/mbuild.mako | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/mako/lib/mbuild.mako b/src/mako/lib/mbuild.mako index dad03dc663..caec9166bd 100644 --- a/src/mako/lib/mbuild.mako +++ b/src/mako/lib/mbuild.mako @@ -146,7 +146,7 @@ ${self._setter_fn(resource, method, m, p, part_prop, ThisType, c)}\ /// Usually there is more than one suitable scope to authorize an operation, some of which may /// encompass more rights than others. For example, for listing resources, a *read-only* scope will be /// sufficient, a read-write scope will do as well. - pub fn scope(mut self, scope: T) -> ${ThisType} + pub fn add_scope(mut self, scope: T) -> ${ThisType} where T: Str { self.${api.properties.scopes}.insert(scope.as_slice().to_string(), ()); self