Skip to content

Review and unify iRODS access constant use #2225

@mikkonie

Description

@mikkonie

There are redundantly multiple ways we refer to iRODS access level constants, from delaring them in module local constants to setting them up in test case member variables (e.g. self.irods_access_own).

These are a mess and should be unified. Can we just use constants from PRC?

This could be done nicely together with #2215.

Metadata

Metadata

Assignees

No one assigned

    Labels

    app: irodsadminIssue in the irodsadmin appapp: irodsbackendIssue in the irodsbackend appapp: taskflowbackendIssue in the taskflowbackend appinternalChanges invisible to the user or APIs (e.g. refactoring and optimization)

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions