Add write operations to Resource #237
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
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.
Adds a new
withOutputStreamoperation onResourcethat saves data to a file on JVM/Native and to localStorage on JS.While
OutputStreamis not a very convenient interface, it is good enough for now... I'm not sure what a higher level interface should look like (writeString?writeBytes?).This helps implementing a hot reload stratagy like the one proposed in #45
Also, this PR the order resources are loaded to always try a file/localStorage first. This way an application can, for example, have an
init.confin the resources with the default configuration and let the user save it's configuration also toinit.conf. If the file is deleted, the application will load back the default config.