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
About a month ago someone opened an issue on this function, but after he/she was asked to move this to the ideas section, nothing happens, so I will try it now...
I am using featmap as a "local" application at work and develop at home on another machine. I would like to transfer some of the quite complex maps done at work to my home machine to test my development done there with these maps. But the feature will be nice in every scenario were different instances of featmap are used.
Meanwhile the issue is closed. On the issue I have offered an idea how this could be handled. Until know I have implemented most of this idea on the level of the command line, which would be sufficient for me. The addition of the code was fairly non invasive, one or tẃo new methods on service and repo, to handle projects/workspaces by name and the export and import functions for the json files. The only part missing is around the featurecomments especially the featurecomment owners because to import a project with these element there have to be rules how missing accounts/members should be handled. Because I am not using this featurecomments at the moment, this is not problem for me.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
About a month ago someone opened an issue on this function, but after he/she was asked to move this to the ideas section, nothing happens, so I will try it now...
I am using featmap as a "local" application at work and develop at home on another machine. I would like to transfer some of the quite complex maps done at work to my home machine to test my development done there with these maps. But the feature will be nice in every scenario were different instances of featmap are used.
Meanwhile the issue is closed. On the issue I have offered an idea how this could be handled. Until know I have implemented most of this idea on the level of the command line, which would be sufficient for me. The addition of the code was fairly non invasive, one or tẃo new methods on service and repo, to handle projects/workspaces by name and the export and import functions for the json files. The only part missing is around the featurecomments especially the featurecomment owners because to import a project with these element there have to be rules how missing accounts/members should be handled. Because I am not using this featurecomments at the moment, this is not problem for me.
Beta Was this translation helpful? Give feedback.
All reactions