Implementation of File Attachments #205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created base models and started user-facing controls.
Also fixed issue with file editing on JS side
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pull request tracks the implementation of File attachments. Attachments will be able to be added to a page, via the page edit view and will be editable and sortable.
Attachments will consist of both file uploads and links to other systems such as box, dropbox, google drive etc. These systems will not be integrated (At least initially) but the attachments area will simply accept a url input.
Uploads will be behind the application, Non publically accessible. To access a file the user must have access to view the page it's been uploaded to. Uploads will be able to be stored on the filesystem or any cloud filesystem Laravel supports by default.
In reference to #62.
Feature Status