- validation script used unmaintained npm package
- switched to actively maintained package from same maintainer
- pipe full output to stdout
- bump node major version in development backend Dockerfile
- fix two api spec errors and two random warnings - boyscout, hell yeah
* create a new component for showing list of NWD
* fix the method for fetching data from the database
* fix eslint errors
* add delete icon to the list of non-working days
* Change componenet name and add empty state handleing and add button for opening the date picker modal
* fix full calendar/list css import issue in anguar 14
* change confirm modal to show a list of data and a warning
* open confirmation modal in list of non-working days component while submitting the form
* format removed dates to be shown on the confirmation modal
* change a warning string
* make a connection between rails and calendar list component
* reinstall list in fullcalendar
* fetch data from non-working days API endpoint
* set suto to content height of calendar
* use id returned from the API
* Fix parameter name on WorkingDaysSettingsController
* Fix non working days attributes _deleted to _destroy
* Pass ruby variable to the op-non-working-days-list component
* fixup! Pass ruby variable to the op-non-working-days-list component
* Pass this.modifiedNonWorkingDays to the angular component
* add inputs to the form itself instead of row of calendar, while adding a new NWD
* Update the modified_non_working_days variable to also propagate the _destroy field to the frontend
* create hidden inputs only for added and deleted NWDs
* Fix specs
* Limit json attributes
* add non-working days as test
* add hidden inputs for a new nwd in ngoninit and add it to the calendar itself at the same time, when it is back from a failed proces
* add a method to check if a date is a NWD
* Add requests spec for deleting non working days
* Allow dangling underscore for _destroy
* fixup! Allow dangling underscore for _destroy
* WIP single date picker
* Use slots from single datepicker to wire up modal
* Add spec to add a NWD
* remove Non-working days only toggle
* WIP
* Add required validation
* show asterisks beside date in date-picker
* test if date ans name are entered then close the datepicke
* Add error when already added
* Rewrite into less implicit created elements
---------
Co-authored-by: Dombi Attila <83396+dombesz@users.noreply.github.com>
Co-authored-by: Oliver Günther <mail@oliverguenther.de>
Squash commit of storybook addition to aid design system documentation efforts.
The older commit titles were:
* Initial storybook commit
* Fix documentation.json links
* Don't track documentation.json in git
* Enable sass in storybook
* Initial version of a story that uses angular components
* Remove example stories, clean up button story
* More example stories
* Fix sb build
* Always use dev
* Try without auth header
* Update workflow name
* More logs
* Check if token set
* Use release/storybook branch for testing
* Send ref input to workflow
* Escape input to curl call
* Adding logging
* Different type of escaping
* Fix JOSN
* Use dev branch for opf/design-system storybook publishing
* Add plugin to message path to parent window
* Remove extraneous story
* Add a ton of docs
* Update stories
* Fix syntax error caused by multiple newlines inside of a JSX component
* Add text-field story
* Add basic html stories that don't work yet
* Try to get plain HTML examples working
* HTML Examples work, but slowly revert to components anyway
* Fix HTML examples
* Remove extraneous files
* Put storybook eslint rules back in
* Improve docs
* Show docs tab by default
* Add pullpreview for storybook
* Use the same pullpreview tag for both storybook and normal deployments
* Change name of second pullpreview workflow
* Pin node version to 16.17.0
* Initial update to docs
Added/updated:
Foundation pages:
- Colours (major update)
- Shadows (minor)
- Typography (new)
Blocks
- Checkbox (minor)
- Action bar (major)
- Buttons (new)
- Link (major)
- Modal Dialogue (new)
- Selector Field (new)
* Make sure all code is available during storybook pp build
* Change storybook pullpreview file name
* Add production target to docker-compose sb pp
* Fix acme check for sb pp
* Only run cd-storybook on dev branch
* Run without https on 8080
* Added intro and new page
- Introduction renamed to "Design System", page rewritten completely
- Added page "Devices and Accessibility"
* Remove domain from caddy
* Add port to listen command
* Remove double pullpreview workflows
* Added Divider component
* Change sorting of stories
* Update section titles and order for styles and blocks
* add extra action bar story
* Updated organising + new page
- Updated organisation into Styles, Components and Patterns.
- Added page "Using Storybook" (mostly a skeleton for now)
* Added note about colours not being implemented yet
* Minor
Co-authored-by: Parimal Satyal <88370597+psatyal@users.noreply.github.com>
- changed /download and /open to redirect responses
- fixed readOnly properties
- added storage path and model
- added permissions and descriptions on error responses
- Use awesome-typescript-loader in WebPack
- Correctly name open-project.typings.d.ts (instead of wronglopen-project.typings.ts)
- Insert typings.d.ts to reference typings-folder outside of app folder
This removes `gulp` and provides a simpler `karma` and `webpack`,
`webpack-watch` npm scripts.
For actual development, users will need the Rails stack anyway, so it
won't make sense to keep a separate set of dependencies up to date.
* Instead of `gulp webpack`, use `npm run webpack`.
* Instead of `gulp watch`, use `npm run webpack-watch`, which is *drastically* faster than gulp watch-polling.
* Instead of `gulp tests:karma` use `npm run karma`, or just `npm test`.
This also removes all traces of express and restores the Rails
styleguide. It is not whitelisted for precompilation and is only
available in the context of the development mode.
To access the styleguide, use `/assets/styleguide.html`.
In agreement with @furinvader, we have decided to remove protractor
testing from OpenProject.
Frontend tests are implemented in karma and test single units of work as
before.
Since the freshness of APIv3 JSON mocks are getting ouf hand and we have
covered almost all E2E protractor tests with Rails, we're going to
resort to Rails to write concise *actual* integration test with correct data.
Alexander Brandon Coles