taiga
/
taiga-front
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Force initialize new_terms_key

stable
Álex Hermida 2018-05-24 16:15:42 +02:00
parent 858917e700
commit 8c68f05101
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
app/modules/components/terms-announcement/terms-announcement.directive.coffee
View File

@ -23,7 +23,7 @@
###
TermsAnnouncementDirective = (TermsAnnouncementService, $repo, $auth, $config) ->
TermsAnnouncementDirective = (TermsAnnouncementService, $repo, $auth, $config, $model) ->
link = (scope, el, attrs) ->
scope.privacyPolicyUrl = $config.get("privacyPolicyUrl")
scope.termsOfServiceUrl = $config.get("termsOfServiceUrl")
@ -38,10 +38,18 @@ TermsAnnouncementDirective = (TermsAnnouncementService, $repo, $auth, $config) -
TermsAnnouncementService.open = false
user = $auth.getUser()
# We need to force initialization of rootscope user if localstorage user
# doesn't have the 'read_new_terms' key
if user.read_new_terms == undefined
userData = user.getAttrs()
userData.read_new_terms = false
user = $model.make_model("users", userData)
user.read_new_terms = true
onSuccess = (data) ->
$auth.setUser(data)
user.read_new_terms = true
$repo.save(user).then(onSuccess)
Object.defineProperties(this, {
@ -57,7 +65,8 @@ TermsAnnouncementDirective.$inject = [
"tgTermsAnnouncementService",
"$tgRepo",
"$tgAuth",
"$tgConfig"
"$tgConfig",
"$tgModel"
]
angular.module("taigaComponents")