openproject/features/step_definitions/add_widget_steps.rb

#-- copyright
# OpenProject My Project Page Plugin
#
# Copyright (C) 2011-2014 the OpenProject Foundation (OPF)
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# 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.md for more details.
#++

Then /^"(.+)" should be disabled in the my project page available widgets drop down$/ do |widget_name|
  option_name = MyProjectsOverviewsController.available_blocks.detect{|_k, v| I18n.t(v) == widget_name}.first.dasherize

  steps %Q{Then the "block-select" drop-down should have the following options disabled:
            | #{option_name} |}
end
Preparing the gem for release; adding project-scoped blocks from other plugins Following the guidelines in https://www.openproject.org/projects/openproject/wiki/Developing_Plugins, the gem was prepared for release * added copyright-headers * added readme * gemspec extended This also fixes an issue with plugins, that want to add views for the my_project_page: The mechanism now looks for blocks in the my_projects_overviews-folder of the plugin and adds them to the configuration using the document's name (Very similar to the way my_page does this in core.) An example for this can be found in the documents-plugin, which now provides views that either show all documents the user can see (in my/_documents.html.erb) and scoped to the given project (under my_projects_overviews/_project_documents.html.erb) 11 years ago			`#-- copyright`
Updated copyright notices 11 years ago			`# OpenProject My Project Page Plugin`
			`#`
			`# Copyright (C) 2011-2014 the OpenProject Foundation (OPF)`
Preparing the gem for release; adding project-scoped blocks from other plugins Following the guidelines in https://www.openproject.org/projects/openproject/wiki/Developing_Plugins, the gem was prepared for release * added copyright-headers * added readme * gemspec extended This also fixes an issue with plugins, that want to add views for the my_project_page: The mechanism now looks for blocks in the my_projects_overviews-folder of the plugin and adds them to the configuration using the document's name (Very similar to the way my_page does this in core.) An example for this can be found in the documents-plugin, which now provides views that either show all documents the user can see (in my/_documents.html.erb) and scoped to the given project (under my_projects_overviews/_project_documents.html.erb) 11 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.`
			`#`
Updated copyright notices and readme 11 years ago			`# 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.md for more details.`
Preparing the gem for release; adding project-scoped blocks from other plugins Following the guidelines in https://www.openproject.org/projects/openproject/wiki/Developing_Plugins, the gem was prepared for release * added copyright-headers * added readme * gemspec extended This also fixes an issue with plugins, that want to add views for the my_project_page: The mechanism now looks for blocks in the my_projects_overviews-folder of the plugin and adds them to the configuration using the document's name (Very similar to the way my_page does this in core.) An example for this can be found in the documents-plugin, which now provides views that either show all documents the user can see (in my/_documents.html.erb) and scoped to the given project (under my_projects_overviews/_project_documents.html.erb) 11 years ago			`#++`

Used dynamic looking for blocks in all plugins instead of some being predefined and adapted translations Also moved some step definitions to the core to be reused by the my page 11 years ago			`Then /^"(.+)" should be disabled in the my project page available widgets drop down$/ do \|widget_name\|`
Fix rubocop issues 9 years ago			`option_name = MyProjectsOverviewsController.available_blocks.detect{\|_k, v\| I18n.t(v) == widget_name}.first.dasherize`
removing false label and having the available filter widget adding widgets onChange -> one click less 13 years ago
			`steps %Q{Then the "block-select" drop-down should have the following options disabled:`
			`\| #{option_name} \|}`
			`end`