14 Commits (d547748b1621f98d9934b3ac83eff0e450282187)

Author	SHA1	Message	Date
Jens Ulferts	de2735f797	implement time entries widget	6 years ago
Jens Ulferts	90f2192306	time entries api - link actions and use correct response on delete	6 years ago
Jens Ulferts	1b0a79c911	spec set_attributes_service	6 years ago
Felix Höffken	95ceb257f6	resolve ulferts requested changes	6 years ago
Felix Höffken	9eed759cd0	[29029] DELETE option for TimeEntries	6 years ago
Oliver Günther	c7e9239212	[29003] Add PATCH api/v3/time_entries/:id endpoint ... Adds updating time entries to APIv3. https://community.openproject.com/wp/29003	6 years ago
Jens Ulferts	9700d938b4	add a PATCH endpoint for grid ... Right now it only mocks the response	6 years ago
Jens Ulferts	08a7ee52b3	introduce time entry create endpoint in api v3 ... The endpoint allows creation of time entries with the fixed attributes project, activities, ... as well as with custom fields that might be configured for time entries. There is no endpoint for form and schema, yet which micht make it difficult for clients to figure out the correct parameters.	6 years ago
Jens Ulferts	d04b86da9c	introduce custom eager loading for work package list ... Reduces the amount of AR models instantiated when handing wp#index requests by: * Calculating part of the checksum for caching in the db. This is done by using the id and the updated_at/on field of associated models whose representation is cached in the wp representer. * Reusing instantiated models for multiple associations. e.g instances of Project are used in various places (the work package itself, it's ancestors and children). Instead of using Rails' eager loading which would instantiate a project potentially once for every association path, the code now assigns the same instance to all those associations. Additionally, the commit streamlines the creation of custom field injected representers. Now only one class is created for all work packages when before it would be one class for every uniq set of custom fields. On top of that, the class can be reused if the set of custom fields does not change.	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
Jens Ulferts	8842558aac	refactor for code quality	7 years ago
Wieland Lindenthal	4e22681e78	User mentions feature (#5897) ... * Extend syntax for linking users via their ID * Allow login names for linking user profiles. * User require_relative for legacy tests * Add specs for login name based user links; Fixes other specs, too. * Notify mentioned users * Notify linked users; - require quotes for login names in user links as login names can contain spaces, dots that are typical word boundaries - Adding specs * For the decision who gets notified due to mentions only the visibility permissions of the recipient are relevant. * Rubucop satisfaction * Add autocomplete for user names to work pack package descriptions and activity - Uses API V3 Principals endpoint. - Extends API endpoint with name filter and name order. - Make it activate when user types an "@" or a "user#" - Still for work packages only. * Directly show a list of users after typing '@' and allow navigating list with cursor keys * Add an '@' before the rendered user link * Adopting spec as WP autocompleter now expects whitespace before hash sign * Adding spec for using user autocompleter * Introduce magic pageSize of 0 for maximum length * Add id filter for principals * Allow pagination for principals and protect from falling back to a too low default value * Fixing specs * fixing typo in spec * Add magic number 0 for user custom fields * Add a toParams method for ApiV3FilterBuilder * User ApiV3FilterBuilder in path helper service * Add test for mentions principals to path helper * WIP * Convert auto complete helper to TS [ci skip]	7 years ago
ulferts	9c8f7f3ca1	read operations for time_entries via api v3 (#5776) ... * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]	7 years ago