[ 
https://issues.apache.org/jira/browse/COUCHDB-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655715#comment-15655715
 ] 

ASF GitHub Bot commented on COUCHDB-3231:
-----------------------------------------

GitHub user iilyak opened a pull request:

    https://github.com/apache/couchdb-couch/pull/211

    Allow fixing users' documents

    Allow adding missing fields:
    - type
    - roles
    
    Allow update of the type field from incorrect value to the correct one
    (currently it suppose to have value 'user').
    
    COUCHDB-3231

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch 
78142-allow-user-to-correct-invalid-user-docs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch/pull/211.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #211
    
----
commit 5763fd772e1dad300cbe66a7b8c48d62bd0417e6
Author: ILYA Khlopotov <[email protected]>
Date:   2016-11-10T23:02:51Z

    Allow fixing users' documents
    
    Allow adding missing fields:
    - type
    - roles
    
    Allow update of the type field from incorrect value to the correct one
    (currently it suppose to have value 'user').
    
    COUCHDB-3231

----


> Allow fixing users' documents
> -----------------------------
>
>                 Key: COUCHDB-3231
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3231
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: ILYA
>
> The current VDU function for user doc is too strict. It accesses the roles 
> and type fields of the current version of the document. This makes it 
> impossible for the user to correct their users' documents. For example if the 
> user have a document without type field they would have to delete the doc and 
> recreate it again. We should allow adding missing fields. Also there is no 
> reason to restrict the update of a type field from incorrect value to the 
> correct one (currently it suppose to have value 'user').



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to