No validation for formState.link as URL or String

[Keshav-0907]

Describe the bug
When creating a new advertisement, there is a missing validation check for the formState.link field. This allows users to input random strings or potentially invalid data.

To Reproduce
Steps to reproduce the behavior:

1. Create an Organization
2. Go to orgads/id=some_id.
3. Click on Create new advertisement.
4. Now you can eneter any random string in the Provide a link for content to be displayed input.

Expected behavior
The formState.link should undergo a validation to ensure that the provided input is a legitimate URL, preventing the submission of arbitrary or invalid strings.

Screenshots

420e2c94-da58-4f7b-9de8-e3c01d8d0e40.mp4

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[palisadoes]

We have a policy of unassigning contributors who close PRs without getting validation from our reviewer team. This is because:

1. We start looking for people to review PRs when you submit them.
2. We often contact them and link to the PR. If the PR is closed the whole effort is wasted.
3. The historical thread of reviewer comments is broken when the work is spread across multiple PRs. The quality of our code is affected negatively.

Please be considerate of our volunteers' limited time and our desire to improve our code base.

This policy is stated as a pinned post in all our Talawa repositories. Our YouTube videos explain why this practice is not acceptable to our Community.

This has been done 3 times.

[akhilender-bongirwar]

I would like to work on this issue

[pushkar707]

Hi, I want to work over this issue

[Keshav-0907]

We have a policy of unassigning contributors who close PRs without getting validation from our reviewer team. This is because:

1. We start looking for people to review PRs when you submit them.
2. We often contact them and link to the PR. If the PR is closed the whole effort is wasted.
3. The historical thread of reviewer comments is broken when the work is spread across multiple PRs. The quality of our code is affected negatively.

Please be considerate of our volunteers' limited time and our desire to improve our code base.

This policy is stated as a pinned post in all our Talawa repositories. Our YouTube videos explain why this practice is not acceptable to our Community.

This has been done 3 times.

We have a policy of unassigning contributors who close PRs without getting validation from our reviewer team. This is because:

1. We start looking for people to review PRs when you submit them.
2. We often contact them and link to the PR. If the PR is closed the whole effort is wasted.
3. The historical thread of reviewer comments is broken when the work is spread across multiple PRs. The quality of our code is affected negatively.

Please be considerate of our volunteers' limited time and our desire to improve our code base.

This policy is stated as a pinned post in all our Talawa repositories. Our YouTube videos explain why this practice is not acceptable to our Community.

This has been done 3 times.

Apologies for closing PRs without validation. I understand the impact on collaboration. I assure you it won't happen again. I appreciate your understanding. Thanks.

[ghost]

Hi @palisadoes I want to contribute on this issue can you plz assign it to me.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.