Deprecate 'slack_username' field in Mentorship System API

[paritoshsinghrahar]

Description

As a member of the app,
I need be able to find members on Zulip Chat,
so that I can talk to the member.

Currently, it's labelled as field slack_username. We have moved to Zulip. I want you to depreciate the field as it serves no purpose anymore across all instances of the REST API.

Mocks

Acceptance Criteria

Update [Required]

• Depreciate slack_username field across all instances of the REST APIs.

Definition of Done

• All of the required items are completed.
• Approval by 1 mentor.

Estimation

[4] hours

[paritoshsinghrahar]

@isabelcosta Is the issue fine. Or does it need more changes?

[priyanshuone6]

Hey, can you please assign this issue to me

[rubyruins]

I would like to work on this!

[paritoshsinghrahar]

@priyanshuone6 I'll assign it to you if you are eager.
But do remember it's Status: On Hold because the scope of the issue may change. And you may need to change the whole code.
It still needs approval from a Team Lead. If you aren't interested, then please inform.

[paritoshsinghrahar]

@SanketDG How do you feel about the scope of the Issue. Any additions or subtractions?

[SanketDG]

Looks good to me, why not just rename to zulip_username.

Deprecation in reality is actually a great idea, but I feel we can easily have a breaking change here to rename.

[priyanshuone6]

So should I depreciate slack_username or should I rename it to zulip_username?

[paritoshsinghrahar]

So should I depreciate slack_username or should I rename it to zulip_username?

We will go with renaming it then to zulip_username. @priyanshuone6

[priyanshuone6]

@paritoshsinghrahar Do I have to rename it to zulip_username in the whole repo?