Replaces all configuration fields currently supported by the api to be fetched from the api instead of from gon. Reduces the information passed to gon. Only the date/time format fields are left for gon to pass as those are not yet available via the api. Adding the fields should be easy.
Unfortunately, representable is broken when passing null values into the
parsing representer. This will result in `property :foo` to be output as
`{ foo: nil }` despite having a reader that writes other stuff.
* Check edit fields for Work package dependencies
* Make EditForm, NotificationService, EditContext indepenedent of Work Packages
* Make EventsService independent of WorkPackages
* Start renaming WpNotificationService (WiP)
* Fix more references
* Fix typescript errors
* Add basic halEditingService
* Rename to global halResourceEditingService (WiP)
* Move typing from class to methods (WiP)
* Fix typescript errors
* Remove space in type
* Add test project widget && generalize the editFieldGroup
* Rename editing portal service
[ci skip]
* Rename WpEditFieldComponent
* Rename WpDisplayFields
* Rename display-XX-field to XX-display-field
[ci skip]
* Add WP specific ID field to distinguish between resources
* Re-add state in work package resource
* Generalize display field renderer
* Rename spent-time to wp-spent-time and fix highlight specifics
[ci skip]
* Actually load the project schema and make field editable
* Make edit-field-group.component an edit-form.component and subclass EditForm
* Remove edit context in favor of specialized EditForm
* Add special cases for work package editing
* Fix edit actions bar
* Fix codeclimate issues
* Use WorkPackageNotificationService if necessary
* Override NotificationService for WPs to allow WP specififc notifications (WiP)
* Correctly provide wpNotification service
Because the ui-router doesn't seem to correctly use the parent element's
injector, we need to provide the wpNotification service not in the
wp-base, but rather the wp-list component as well as in the isolated
query space.
* Allow to filter halEvents for specific resourceTypes (e.g. WorkPackage)
* Remove superfluous cell class constant
* Start renaming selectors for wp-edit-field into generics
* Remove wp-table--cell-span in favor of display field selector
* Consolidate other display and edit field styles
* Provide specialized service for transitions in active edit forms
* Remove superfluous overflowSelector
* Accept that date field contains some work package specifics
* Ignore unreadable files
* Provide the changeset for work packages as a hook
Since hal resource editing service is provided per query space, we
cannot register them once (would only work globally)
* Fix dangerfile
* Remove another todo in halResourceNotification service
* Fix npm TestBed for changed dependencies
* Show inplace edit field in project details widget
* Fix highlighting in single view
* Provide HalResourceEditingService outside of project context
* Used typedState for single-view
* Also provide wpNotification service in split view
* Correct check for resource type in eventsService
* Fix getSchemaName in display field renderer
* Fix passing ids into `halEditing.stopEditing`
* Do not globally inject the halResourceEditingService
There's a bug(?) in ui-router that gives you the global service before
the parent injected service for a ui-view
* Fix wpCreate service on copying and parallel creation
* Remove test project widget
* Revert changes for project details widget
Replaces all configuration fields currently supported by the api to be fetched from the api instead of from gon. Reduces the information passed to gon. Only the date/time format fields are left for gon to pass as those are not yet available via the api. Adding the fields should be easy.
Oliver Günther
ulferts
Henriette Dinger
Wieland Lindenthal
Markus Kahl