Hi Artem, we had an <issue> come up that we'd like...
# dev-frontend
c
Hi Artem, we had an issue come up that we'd like to add to this week's sprint. It's a high priority which is why I am messaging about it. Obviously it's a little late to add stuff. If we bump some of the lower priority stuff that you're currently assigned, do you think that we could squeeze this issue in this week?
I think it is pretty much just adding an input field in an existing page.
lmk if that's possible. sorry for the last minute change.
a
sure lets add it
👍 1
c
@Chris (deprecated profile) fyi
a
I will try to have done as much as possible
c
thanks!
I updated the description to add some text of how this field will be used in the short term vs long term
a
Guys we also need to add connectionName here  
/v1/web_backend/connections/list
/v1/web_backend/connections/get
apart from that my changes are ready. Will take care of it in the morning if you don’t have a time for it.
c
@Chris (deprecated profile) can you knock out those API changes in the morning for artem?
c
I just pushed another commit with the missing webbackend stuff
I haven’t completely double checked if anything is still missing yet though but will keep looking at it tomorrow
a
jamakase/add-connection-name-field this is the branch with implementation but I am trying to build backend now to test.
c
👌
Thanks!
@Artem Astapenko from code review comments, i renamed the field
connectionName
to
namespaceDefault
a
ok. Let me rename that in my branch
@Chris (deprecated profile) I have small problem:
/v1/web_backend/connections/update
 is not updating 
namespaceDefault
I send
Copy code
{
  connectionId: "63146393-4aa8-4914-9c69-83b29fc5c085"
  namespaceDefault: "/my"
  schedule: null
  ...
}
and receive
Copy code
{
  connectionId: "63146393-4aa8-4914-9c69-83b29fc5c085"
  namespaceDefault: "/test-prefix"
  schedule: null
  ...
}
c
Ok i’ll take a look
I pushed new changes around the read/update of that field in the API, it should be fixed on my branch now
👌 1