This error is intended for cases when a method is
intentionally not implemented, because the module/class defining
it expects a subclass (or class including the module) to implement
the method.
This is intended to distinguish it from other cases, such as:
* feature not implemented yet
* edge case of a method call not yet supported
Notably it avoids the misuse of the Ruby-defined NotImplementedError,
which is only intended for much more specific scenarios:
> Raised when a feature is not implemented on the current platform. For example, methods depending on the fsync or fork system calls may raise this exception [...]
Also see https://docs.ruby-lang.org/en/master/NotImplementedError.html
Builds a new filter strategy together with an extended set of operators
used specifically for this filters. It consists of a classic
"list_optional" filter strategy with a couple of modifications.
1. We reset the "=" symbol back to an "Equals"
1. We override the "*" symbol to use the new custom "Any" operator
2. We override the "!*" symbol to use the new custom "None" operator
* Add customized operator that allows subselect on custom_values
* Override operators and labels for list values and change defaults
* Improve class check for determining operator
* Add spec for is (AND) operator
* Adapt specs to renamed operators
* Add operator to doc
The default BooleanEquals filter treats null same as false. Because of that, notifications that are not meant for ian were displayed. The BooleanEqualsStrict filter only filters for false as expected so that the notifications are not displayed.
Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded.
Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013
* order independent contains operator
This for example affects the search which relies on the subject filter with the contains operator being active.
* remove legacy query spec
The query is generally covered rather well in the new specs.
[ci skip]
That way, we can treat the end point as just another wp endpoint with
filter capabilities. Currently, there is a couple of custom logic still
present but that is only due to wanting to not break the public API.
In the long run, the whole end point could be removed as the same
filtering is now available using /api/v3/work_packages with an
appropriate filter.
* Hack spike to show D&D use case
[ci skip]
* Add ordered work packages
* Save order on existing work packages
* Boards WIP
* CDK drag
* Add dragula handler
[ci skip]
* Add filter to return all manual sorted work packages
* Print icon on hover
* Boards routing and list components
* Better loading indicator on list with streaming result
[ci skip]
* Add new board and list buttons
[ci skip]
* Post new query
[ci skip]
* Added creation of new board lists with persisted queries
[ci skip]
* Render placeholder row in empty queries
[ci skip]
* Push boards on grid
* Use base class in scope
[ci skip]
* Extend api for options
* Hack spike to show D&D use case
[ci skip]
* Add ordered work packages
* Save order on existing work packages
* Boards WIP
* CDK drag
* Add dragula handler
[ci skip]
* Add filter to return all manual sorted work packages
* Print icon on hover
* Boards routing and list components
* Better loading indicator on list with streaming result
[ci skip]
* Add new board and list buttons
[ci skip]
* Post new query
[ci skip]
* Added creation of new board lists with persisted queries
[ci skip]
* Render placeholder row in empty queries
[ci skip]
* Save queries in grids
[ci skip]
* Renaming queries
[ci skip]
* Add existing work packages to board
[ci skip]
* Introduce card view component for work packages
* Extend grids to allow project scope for boards (#7025)
Extends the grid backend to also be able to handle boards. In particular, it adds the ability of boards to be attached to projects and changes the page property of grids to a scope property that better describes that more than one board can belong to the same scope (e.g. /projects/:project_id/boards).
For a fully featured board, though, widgets need to be able to store options, so that they can store queries. Those widgets might also need to have custom processing and validation. That part has not been implemented.
* introduce project association for boards
* have dedicated grid registration classes
* update and create form for board grids
* extract defaults into grid registration
[ci skip]
* Add drag and drop to card view
[ci skip]
* Add options to grid
* Fix option migration name
* Renaming boards
[ci skip]
* Frontend deletion of boards
* Avoid map on NodeList which doesnt exist
[ci skip]
* Add inline create to boards
[ci skip]
* Smaller create button
[ci skip]
* Add navigation for boards
* Make inner grid same height
* Replace index page with table
* Workaround for widget registration
[ci skip]
* Fixed height for cards and tables
[ci skip]
* Implement escape as cancel d&d action
[ci skip]
* Fix and extend grid specs for name and options
* Extend board specs for required name
* Fix migration for MySQL references
https://stackoverflow.com/a/45825566/420614
* Make board list extend from widget
Since we cannot configure widgets yet, it's not yet possible to use a
board-list widget anywhere.
* Fix specs
* Fix escape listener removal
[ci skip]
* Fix renamed to_path in relation spec
[ci skip]
* Allow deletion of grids for boards
* Avoid reloading resource multiple times with replays
* Frontend synchronization on deletion
[ci skip]
* Delete through table
* Use work packages board path
* Use work packages board path
* Fix augmented columns breaking re-rendering
* Fix duplicated permission with forums
* Strengthen tab switch in specs
* Add hidden flag for project-context queries
Allows the API to create a hidden query that will not be rendered to the
user even if it is within a project context.
* private queries
* Add hidden flag for project-context queries
Allows the API to create a hidden query that will not be rendered to the
user even if it is within a project context.
* Move boards below work packages
* Add Board configuration modal
* Fix reloading with onPush
* Saving / Switching of display mode
[ci skip]
* Extract wp-query-selectable-title into common component
* Fix renaming of board-list
* Fix auto-hide notifications in boards
* Add permissions to seeders
* Reorder lists in board
* Linting
* Remove default gravatar from settings
* Show assignees avatar in the card view of WPs
* Fix specs
* Add missing method
* Fix timeline icon
* Use URL as input to be able to show avatars for groups, too
* Fix test
* Add further specs
* Use correct data attribute to avoid unnecessary data base calls
* Add further specs
* Deletion of board lists
* Pass permission via gon to decide whether we can create boards
* Fix rename spec
* Cherry-pick of 7873d59 and 30abc7f
* replace rails based calendar with angular
* render empty calendar
* update query on month switch
* introduce specific interval filter
* show colors
* remove now unused filter partial
* start on retaining the view in the url
* hide datesInterval filter
* I18n for calendars title
* stengthen explicity of expected filters
* spec moving to the next month
* fix FilterSerializer reference
* remove outdated feature spec
* rework calendar controller specs
* avoid undefined columns
* bump ng-calendar to 1.7.0
* Revert "fix FilterSerializer reference"
This reverts commit 2bb2e574cdd664a02a4eb9c3e94b5a170aec0a67.
* Revert "avoid undefined columns"
This reverts commit bcbb381b34b095526d3ee1aa15d6263a658c03c0.
* load initial query only after calendar has been loaded
* implement month remembering
* implement history back and forth
* cleanup code
* remove unused methods
* remove order value from filters
* replace rails calendar widget completely
* fix shrinkwrap
* move module into correct namespace
* linting
* remove unused js
* calculate full calendar height dynamically
* setting calendar locale from service
* retain week on reload
* show notification in case of too many results
* show tooltip on hover
* go to work package on click
* deactivate tooltip before wp show
* narrow down style to tooltip
* [28885] Improve html title consistency when navigating to queries
Currently, query names are not reflected in the HTML title. This results in 'wrong' titles being shown when entering a split or full view and then returning back to the list.
https://community.openproject.com/wp/28885
[ci skip]
Oliver Günther