Closed naluinui closed 4 months ago
The problem is that legacy is generating the url/slug itself, you can see the problem here: https://github.com/rfcx/arbimon-legacy/blob/5ef38dfd2c92d3bd23acbd3ae9f460399e75444b/app/routes/data-api/integration.js#L22
Suggested fix:
findUniqueUrl
from everywhere in the codebase - Legacy is not allowed to define the url/slugExtra:
description
from create project endpoint on legacy as that is no longer neededThe problem is that legacy is generating the url/slug itself, you can see the problem here:
Suggested fix:
- Remove
findUniqueUrl
from everywhere in the codebase - Legacy is not allowed to define the url/slug ...
That's not going to work because the create project is called from Core and Core doesn't have the slug.
New suggested fix:
I've added a url
parameter to the update endpoint on legacy: https://github.com/rfcx/arbimon-legacy/commit/70aefee82005a0ccd3a938da70e6af4a3b8c554c
Released on production https://github.com/rfcx/arbimon/actions/runs/9009608086
Describe the bug When you create a new project, the slug or url that was auto generated were different between bio and legacy. For example, my project called "TEst". Bio's auto generated slug was
t-est
where as in legacy it was${core_project_id}_test
. (I tested it on staging and my legacy's project id is 5858)To Reproduce Steps to reproduce the behavior:
Expected behavior Url should be the same in bio and legacy
Screenshots Related problem from this issue
https://github.com/rfcx/arbimon-legacy/assets/9149523/05de2ea8-46fa-4e77-b0e0-dd1d7ed9aded
Context