TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32605 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: b2111d0d07
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b2111d0d07'
${ noResults }
openproject/app/models/queries/users.rb

42 lines
1.9 KiB
Raw Normal View History Unescape

lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
#-- encoding: UTF-8
fixes filtering members by group (#5800) additionally fixes: * with "all" selected, all members are shown, not only those being active, invited or registered * with "locked" selected, locked users are now displayed. * the Project#members_principals associations lacked the `references` method which lead to the users table being undefined in the resulting query. In order to achive the bug fixes, the member filtering is now based on the query engine also used for users, queries, work_packages, ... As a lot of the members filters are very similar to user filters (in fact, a lot of the members filter work on the users model), those filters are shared via modules. [ci skip]
7 years ago
lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
#-- copyright
# OpenProject is a project management system.
Update copyright notice
8 years ago
# Copyright (C) 2012-2017 the OpenProject Foundation (OPF)
lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# OpenProject is a fork of ChiliProject, which is a fork of Redmine. The copyright follows:
Update copyright notice
8 years ago
# Copyright (C) 2006-2017 Jean-Philippe Lang
lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
# Copyright (C) 2010-2013 the ChiliProject Team
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
#
# See doc/COPYRIGHT.rdoc for more details.
#++
add user query and enabled it in the users api
8 years ago
module Queries::Users
Queries::Register.filter Queries::Users::UserQuery, Queries::Users::Filters::NameFilter
Queries::Register.filter Queries::Users::UserQuery, Queries::Users::Filters::GroupFilter
Queries::Register.filter Queries::Users::UserQuery, Queries::Users::Filters::StatusFilter
added login filter; fixed status filter
8 years ago
Queries::Register.filter Queries::Users::UserQuery, Queries::Users::Filters::LoginFilter
fixes filtering members by group (#5800) additionally fixes: * with "all" selected, all members are shown, not only those being active, invited or registered * with "locked" selected, locked users are now displayed. * the Project#members_principals associations lacked the `references` method which lead to the users table being undefined in the resulting query. In order to achive the bug fixes, the member filtering is now based on the query engine also used for users, queries, work_packages, ... As a lot of the members filters are very similar to user filters (in fact, a lot of the members filter work on the users model), those filters are shared via modules. [ci skip]
7 years ago
Queries::Register.filter Queries::Users::UserQuery, Queries::Users::Filters::BlockedFilter
lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
add user query and enabled it in the users api
8 years ago
Queries::Register.order Queries::Users::UserQuery, Queries::Users::Orders::DefaultOrder
Queries::Register.order Queries::Users::UserQuery, Queries::Users::Orders::NameOrder
Queries::Register.order Queries::Users::UserQuery, Queries::Users::Orders::GroupOrder
lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.
8 years ago
end