* Bump ng2-charts to ^8.0.0
* Bump chart.js to 4.5.0
* Update imports, providers using default config
* Remove chart.js dependencies from CJS allowlist
These dependencies are now provided as ESM.
* Revert A11y-related Chart colour changes
These improvements were intended to improve the contrast (and thus
accessibility) of bar charts rendered by the Work Packages Overview
widget. However, the solution as implemented, when combined with the
upgrade to ng-charts2 8.0.0, breaks styling of non-bar charts rendered
by the Work Packages Graph widget.
This partially reverts commit 89135ae36c.
Force updates Angular dependencies:
ng update @angular/core@20 @angular/cli@20 --force
And performs automated upgrade:
- Moves imports of `DOCUMENT` from `@angular/common` to `@angular/core`.
- Replaces usages of the deprecated InjectFlags enum.
* Update angular to v15
Also bumps fullcalendar to v6-beta to be compatible
Bump fullcalendar to v6 final
* Fix accessing readOnly property that no longer exists
* Replace content projection
* Fix confusing duplicate variables scss, sass file
One can be imported by helpers, the other not
* Upgrade angular to 12.0
* Fix TS errors after upgrade
* Upgrade pako and fix usage of deflate
Pako 2 no longer outputs binary encoded strings, so we need to use a separate helper lib
* Better spec error reporting and fix beforeunload spec
* Bump node compiler size
* Let GitHub integration show changes in a separate tab
* added new github integration icons to icon font
* add tab content: working tab-header and copy-menu
* modernise github_integrations ruby code
* refactored some code to be more modern ruby (if wrote most of it 7
years ago and couldn't look at some parts without squinting too much)
* make some intended-to-be-private module methods actually private
* fixed all rubocop errors in the /modules/github_integration
* re-organized tests a little
* gave our rubocop.yml some RSpec-related defaults -- happy to discuss
these, but I think we can live with these as a good starting point
👆 all without actually (intentionally) changing the behaviour
* removed dead angular template code
* codeclimate found more things than rubocop :)
* removed create-pr-button since we decided against implementing that feature
* added missing translations
* properly cache the github related part of the wp api
* lower case pull requests in translations
* fix specs
* [35527] Add quick add button menu in top menu
* Add quick menu item to top menu
* Refactor top_menu.sass to follow BEM
* Only render project-based path if persisted
* Render project types when in project context
* Add headline and determine if any types are visible
* Hide quick add menu for unauthorized users
* Fix login menu dropdown by adding class
* Add schematic for correctly generating components
* Add augment service for triggering invite user modal
* Fix allowed_to? check in menu
* Add spec
* Highlight types and show all
* Fix help menu overridden
* Extend spec
* Add parent_id to project in dropdown and expand advanced settings
* Reload the page if the modal returned any data
* Fix invalid url allowed check if there is no URL to check
* Restrict top_menu sass
* Remove unused imports
* Reduce required permissions to show quick add
* Spec review feedback
* Rename project fieldset ID
* tslint to eslint migration
* Autofix issues
* Fix codeclimate path to eslintrc
* Extend linter config for use with ng lint
* Change prefix to op in angular lints
* Bump Angular to 11
* Bump fullcalendar
* Bump uirouter
* bump typescript and rxjs
fixup! bump typescript and rxjs
* Run angular update migrations
* Fix deprecated options in serve, they are kept in builder
* Replace node-sass with sass and fix errors
* Include all ts files again to fix warnings
We have scripts that should be contained but are only loaded dynamically. It seems this trips up TS
to print warnings that these files are unused, which they really aren't.
* Address typescript compilation errors and warnings due to 4.0 upgrade
* Link to styles.css not js with updated sass
* Only reposition dropdown if appendTo is set
* Initialize resource property in edit field component
Correctly update field component and handler properties
Always use the changeset schema
Fix removed property in custom text
Importing relative assets from components will get them output to the
deployPath and prepended with the `deployUrl`.
This unfortunately is static, and not supported with our
RELATIVE_URL_ROOT rails option, which currently does not trigger
compilation.
On cloud, this is not a problem so enabling this option for the
subscription plugin
* Show icon next to start date depending on the scheduling mode
* Show modal when opening date edit fields which shall be able to change the dates and the scheduling mode
* Introduce flatpickr as a datepicker for the modal of the dateEditField
* Use new datepicker within opDatePickerComponent
* Reuse existing Datepicker class for better code abstraction
* Set dates only when Instance is ready
* Let augmentedDatePicker use generic DatePicker class, too.
* Remove jQuery UI datepicker specific styles as they do not apply any more.
* Use localized strings in new datepicker
* Close datepicker only on click outside
* Allow single and multi selection of dates and save changes
* Update schedulingMode button correctly && remove unused method
* Show combined field for start and end date within the WP single view
* Show normal datepicker for most date fields and the modal with the extended datepicker only for startDate
* Add datepicker edit field and component helper
* Correctly save start and end date
* Show correct default value for dateEditFields && Adapt some tests to new datepicker and combined date field
* Fix date editor spec
* Fix expecting datepicker for start/due date as milestone
* Prevent overflow on body by using modal-portal class && make edit input for combinedDates visible again to show something in a create form
* Only output one debounced change event for op datepicker
* Show combined datepickerModal for dueDate in table, too && save correct scheduling value
* Hide modal if the showing component gets destroyed
* Correctly check for closed datepicker
* Add spec for toggling scheduling mode
* Fix setting dates to modal
* Avoid too many (unnecessary) close events and use keydown instead
* Fix date setting and add custom field date spec
* Change layout of combined date picker modal
* Switch from a range date picker to a multiple selection in order to be able to set only start or due date && Highlight date field that is changed next
* Highlight range manually
* Highlight dueDate initially when the user clicked on the due date field && handle special case that one of the values is not set yet. In this case we don't want to keep both values but only the newly clicked.
* Move helper functions to own class && Improve the range selection to be able highlight ranges over multiple months && Prevent that a start date > due date can be chosen by setting minDate and maxDate
* Adapt test to new way of changing the scheduling mode
* Handle case that the user clicks on a already selected date and thus deselects it
Co-authored-by: Oliver Günther <mail@oliverguenther.de>
Alexander Brandon Coles