Commit dd0812d1 authored by Jörg Richter's avatar Jörg Richter

REST client: adapt 2 topicmaps requests

See dmx-platform/dmx-platform#341
parent 6800d209
Pipeline #10024 passed with stage
in 1 second
......@@ -301,7 +301,7 @@ export default {
// Note: no debounce here; consecutive calls might relate to *different* topics
setTopicPosition (topicmapId, topicId, pos) {
roundPos(pos, 'x', 'y')
http.put(`/topicmaps/${topicmapId}/topic/${topicId}/${pos.x}/${pos.y}`)
http.put(`/topicmaps/${topicmapId}/topic/${topicId}/x/${pos.x}/y/${pos.y}`)
},
// Note: no debounce here; consecutive calls might relate to *different* topic collections
......@@ -314,7 +314,7 @@ export default {
},
setTopicVisibility (topicmapId, topicId, visibility) {
http.put(`/topicmaps/${topicmapId}/topic/${topicId}/${visibility}`)
http.put(`/topicmaps/${topicmapId}/topic/${topicId}/visibility/${visibility}`)
},
// TODO: setAssocVisibility()? Actually not needed by DMX webclient.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment