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, when creating a new mapping we are generating a random id for passing the same in the request, as the in parameter in the service is required.
But in current scenario as well, we are using the id returned from the api (which is an auto generated id) and we are using the same to identify the mappings.
Expected behavior
Need to remove the code for generating the id, once the id param will become optional
Steps to reproduce the issue
Can you handle fixing this bug by yourself?
YES
NO
Environment details
Browser:
OS:
Code Version:
Additional information
The text was updated successfully, but these errors were encountered:
Current behavior
Currently, when creating a new mapping we are generating a random id for passing the same in the request, as the
in
parameter in the service is required.But in current scenario as well, we are using the id returned from the api (which is an auto generated id) and we are using the same to identify the mappings.
Expected behavior
Need to remove the code for generating the id, once the id param will become optional
Steps to reproduce the issue
Can you handle fixing this bug by yourself?
Environment details
Additional information
The text was updated successfully, but these errors were encountered: