Balthazar Berling KelpeandGitHub
37fd36275a
* Max changes from f0ecf9dd4c7503c1562fcadb54ce61873b1f7c6f in photowall repo * Erik's changes from 50af018a07dcea44d755bcc23e84537db90f321a in photowall repo * Update image-editor.js in README.md * Prettify * Max changes from f0ecf9dd4c7503c1562fcadb54ce61873b1f7c6f in photowall repo in output * Erik's changes from 50af018a07dcea44d755bcc23e84537db90f321a in photowall repo in output * Remove "Show 3d image" button and functionality * Output image-editor.js file * Rename the outputted file from image-editor.js to generated-image-editor.js * Output again the file that time as generated-image-editor.js * Update README.md * Remove comma / lint
18 lines
710 B
Markdown
18 lines
710 B
Markdown
# Photowall Image Editor
|
|
|
|
Image editor for the Photowall web project
|
|
|
|
# Working with image-editor integrated in photowall site
|
|
|
|
A suggested workflow is replacing `src/js/legacy/vendor-js/generated-image-editor.js` in photowall project with a symlink to
|
|
`dist/generated-image-editor.js` in this project. That way you can have `gulp watch` running to build on change in this project
|
|
which will trigger `npm run watch` (webpack) in photowall project.
|
|
|
|
Symlink should be removed and new copy of `dist/generated-image-editor.js` copied to photowall project when work
|
|
is done however to not force all team members to have same file structure for projects.
|
|
|
|
# Linting
|
|
|
|
Linting can be run manually with
|
|
`npm run lint`
|