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
Currently the UI parses large links and decomposes them in different options/configuration to pass on to the notebook service.
This is incredibly brittle and hard to maintain, also to maintain backwards compatibility.
Having a link shortener for this application would be ideal. Then the link ID or something like that would be related to parameters saved in our database. The simplest implementation for this is to make all shortened IDs usable/readable by anyone but editable only by the user who created them.
This was directly requested by Volodymyr and would be useful for others that want to share links in publications or in public posts that drops them straight into a Renku session.
Also we can do migrations of the data stored in the database when the notebooks API changes or when any other related API changes.
The text was updated successfully, but these errors were encountered:
Currently the UI parses large links and decomposes them in different options/configuration to pass on to the notebook service.
This is incredibly brittle and hard to maintain, also to maintain backwards compatibility.
Having a link shortener for this application would be ideal. Then the link ID or something like that would be related to parameters saved in our database. The simplest implementation for this is to make all shortened IDs usable/readable by anyone but editable only by the user who created them.
This was directly requested by Volodymyr and would be useful for others that want to share links in publications or in public posts that drops them straight into a Renku session.
Also we can do migrations of the data stored in the database when the notebooks API changes or when any other related API changes.
The text was updated successfully, but these errors were encountered: