* fix(media_folder_relative): use collection name in unpublished entry
* refactor: pass arguments as object to AssetProxy ctor
* feat: support media folders per collection
* feat: resolve media files path based on entry path
* fix: asset public path resolving
* refactor: introduce typescript for AssetProxy
* refactor: code cleanup
* refactor(asset-proxy): add tests,switch to typescript,extract arguments
* refactor: typescript for editorialWorkflow
* refactor: add typescript for media library actions
* refactor: fix type error on map set
* refactor: move locale selector into reducer
* refactor: add typescript for entries actions
* refactor: remove duplication between asset store and media lib
* feat: load assets from backend using API
* refactor(github): add typescript, cache media files
* fix: don't load media URL if already loaded
* feat: add media folder config to collection
* fix: load assets from API when not in UI state
* feat: load entry media files when opening media library
* fix: editorial workflow draft media files bug fixes
* test(unit): fix unit tests
* fix: editor control losing focus
* style: add eslint object-shorthand rule
* test(cypress): re-record mock data
* fix: fix non github backends, large media
* test: uncomment only in tests
* fix(backend-test): add missing displayURL property
* test(e2e): add media library tests
* test(e2e): enable visual testing
* test(e2e): add github backend media library tests
* test(e2e): add git-gateway large media tests
* chore: post rebase fixes
* test: fix tests
* test: fix tests
* test(cypress): fix tests
* docs: add media_folder docs
* test(e2e): add media library delete test
* test(e2e): try and fix image comparison on CI
* ci: reduce test machines from 9 to 8
* test: add reducers and selectors unit tests
* test(e2e): disable visual regression testing for now
* test: add getAsset unit tests
* refactor: use Asset class component instead of hooks
* build: don't inline source maps
* test: add more media path tests
* feat: commit media with post - initial commit
* feat: add draft media indication
* feat: sync UI media files with GitHub on entry load
* feat: bug fixes
* feat: delete media files from github when removed from library
* test: add GitHub backend tests
* test: add unit tests
* fix: meta data object files are not updated
* feat: used nested paths when update a tree instead of recursion
* feat(test-backend): update test backend to persist media file with entry
* test(e2e): re-record fixtures data
* chore: code cleanup
* chore: code cleanup
* fix: wait for library to load before adding entry media files
* chore: code cleanup
* fix: don't add media files on entry when not a draft
* fix: sync media library after draft entry was published
* feat: update media library card draft style, add tests
* test: add Editor unit tests
* chore: test code cleanup
* fix: publishing an entry from workflow tab throws an error
* fix: duplicate media files when using test backend
* refactor: fix lodash import
* chore: update translations and yarn file after rebase
* test(cypress): update recorded data
* fix(test-backend): fix mapping of media files on publish
* add GitHub GraphQL api initial support
* support mutiple backends for e2e tests - initial commit
* add github backend e2e test (currently skipped), fix bugs per tests
* refactor e2e tests, add fork workflow tests, support fork workflow in GraphQL api
* remove log message that might contain authentication token
* return empty error when commit is not found when using GraphQL (align with base class)
* disable github backend tests
* fix bugs introduced after rebase of GraphQL and OpenAuthoring features
* test: update tests per openAuthoring changes, split tests into multiple files
* fix: pass in headers for pagination requests, avoid async iterator as it requires a polyfill on old browsers
* test(e2e): disable github backend tests
Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.
It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.
