You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This used to be a feature of bos-workspace 0.0.1, but was only partially carried over from the refactor. To be completed after #99.
The purpose of the command is to upload other data, besides widget to the social contract. As you can see, looking at an account's data tree on social contract, see every.near's here, there can be other data aside from widget such as "type", "thing", "project"... we want to enable the ability to manage and upload these files from bos-workspace.
The prior implementation of this can be found HERE, feel free to use it as a reference. In short, it loops through all the files in designated directories and builds a large data.json, converts to base64, then uploads to social contract via near cli command.
I think in the new implementation, we should do the same, but associate it with a configuration in the bos.config.json that designates which directories should be uploaded. For example:
Where the strings in "include" are references to the directory names in same level as the bos.config.json. An example of a repository that would use this feature is hyperfiles.
Acceptance criteria
Upload command uploads data to social.near contract
Command throws error if an "included" directory does not exist
Test coverage
should throw error if included directory does not exist
should call social contract with correct values & base64 encoded json
The text was updated successfully, but these errors were encountered:
This used to be a feature of bos-workspace 0.0.1, but was only partially carried over from the refactor. To be completed after #99.
The purpose of the command is to upload other data, besides
widget
to the social contract. As you can see, looking at an account's data tree on social contract, see every.near's here, there can be other data aside fromwidget
such as "type", "thing", "project"... we want to enable the ability to manage and upload these files from bos-workspace.The prior implementation of this can be found HERE, feel free to use it as a reference. In short, it loops through all the files in designated directories and builds a large data.json, converts to base64, then uploads to social contract via near cli command.
I think in the new implementation, we should do the same, but associate it with a configuration in the
bos.config.json
that designates which directories should be uploaded. For example:bos.config.json
Where the strings in "include" are references to the directory names in same level as the bos.config.json. An example of a repository that would use this feature is hyperfiles.
Acceptance criteria
The text was updated successfully, but these errors were encountered: