Files 4.0 #87
Merged
Files 4.0 #87
Conversation
This change includes a brand new implementation for Files, that keeps most of the public API intact, while modernizing the underlying implementation. Under the hood, Files now uses value types and protocols, rather than class inheritance - which improves the type safety of the API, and streamlines the underlying code. Error handling is also improved to include more underlying info, and the docs have been reworked to be much more thorough. The API has also been fine-tuned and modernized, dropping the `FileSystem` class in favor of more “Swifty” APIs on `Folder`, introducing more options for creating new files and folders, and making it possible to easily change properties on file system sequences. A list of all changes will be posted as part of this version’s release notes.
|
I don't really understand why |
|
@bernikovich from the release notes
|
|
Hello. It is a nice framework. But where is new docs? How to create a Folder without FileSystem? |
|
Hope this’ll help |
gwikiera
added a commit
to gwikiera/Files
that referenced
this pull request
May 8, 2020
Files 4.0 This change includes a brand new implementation for Files, that keeps most of the public API intact, while modernizing the underlying implementation. Under the hood, Files now uses value types and protocols, rather than class inheritance - which improves the type safety of the API, and streamlines the underlying code. Error handling is also improved to include more underlying info, and the docs have been reworked to be much more thorough. The API has also been fine-tuned and modernized, dropping the `FileSystem` class in favor of more “Swifty” APIs on `Folder`, introducing more options for creating new files and folders, and making it possible to easily change properties on file system sequences. A list of all changes will be posted as part of this version’s release notes.
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.
This change includes a brand new implementation for Files, that keeps most of the public API intact, while modernizing the underlying implementation.
Under the hood, Files now uses value types and protocols, rather than class inheritance - which improves the type safety of the API, and streamlines the underlying code. Error handling
is also improved to include more underlying info, and the docs have been reworked to be much more thorough.
The API has also been fine-tuned and modernized, dropping the
FileSystemclass in favor of more “Swifty” APIs onFolder, introducing more options for creating new files and folders, and making it possible to easily change properties on file system sequences.A list of all changes will be posted as part of this version’s release notes.