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.
We're able to use local widgets, but what if I want to reference local data when I do bos-workspace dev?
For example, I have a Social.get(${config_account}/project/nested.projectId) in my code to reference the JSON I have stored at project/nested/projectId in my 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.
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.
This data should be exposed through the dev server so it is used during RPC proxy, see in lib/server. It could use the same devJson, just save outside of "components".
Acceptance criteria
Local data can be referenced in workspace code
Throws error if an "included" directory does not exist
Should watch for changes in included directories
Test coverage
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.
We're able to use local widgets, but what if I want to reference local data when I do
bos-workspace dev
?For example, I have a
Social.get(${config_account}/project/nested.projectId)
in my code to reference the JSON I have stored atproject/nested/projectId
in my 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.
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.
This data should be exposed through the dev server so it is used during RPC proxy, see in lib/server. It could use the same devJson, just save outside of "components".
Acceptance criteria
The text was updated successfully, but these errors were encountered: