Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update __repr__() method models.py #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
consarnproject wants to merge 1 commit into keploy:main
base: main
Choose a base branch
Loading
from consarnproject:patch-1

Conversation

@consarnproject
Copy link

@consarnproject consarnproject commented Jun 18, 2025

I chose this additional piece of code (which.. "makes an attempt to return a string that would yield an object with the same value when passed to eval()") because models and test_crud are important in order to have the testing phase of this application work correctly. In the testing phase it is important to have access to printable versions of objects to see and determine what they contain. It is important to be able to easily access what an object contains easily via printing so that at any point of the complex process of testing, the developer can refer to and "evaluate" any object in the correct way.

I chose this additional piece of code (which.. "makes an attempt to return a string that would yield an object with the same value when passed to eval()") because models and test_crud are important in order to have the testing phase of this application work correctly. In the testing phase it is important to have access to printable versions of objects to see and determine what they contain. It is important to be able to easily access what an object contains easily via printing so that at any point of the complex process of testing, the developer can refer to and "evaluate" any object in the correct way.
Copy link

@pratik-mahalle pratik-mahalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @consarnproject, Thanks for raising this pr.
Unfortunately, this PR doesn’t include any meaningful changes, typos and breaking links are supposed or just content changes are to be reported not fixed. You can do so on the specific two repositories that we provided. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were supposed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

Copy link
Author

consarnproject commented Jun 30, 2025 via email

Thank you for your message Pratik. Should I go ahead and create a new PR that is more meaningful or am I ok thus far ? Kindest, Andrew
...
On Fri, Jun 27, 2025 at 7:58 AM Pratik Mahalle ***@***.***> wrote: ***@***.**** commented on this pull request. Hey @consarnproject <https://github.com/consarnproject>, Thanks for raising this pr. Unfortunately, this PR doesn’t include any meaningful changes, typos and breaking links are supposed or just content changes are to be reported not fixed. You can do so on the specific two repositories that we provided. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized. This being a part of an assignment in api fellowship would be counted since you were supposed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now. — Reply to this email directly, view it on GitHub <#47 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7RWKPXFJT3ZXEA47XZWJCD3FTMRHAVCNFSM6AAAAAB7SVSN3KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDSNRUHA3TKNZRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Copy link

Yeah, go ahead @consarnproject

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@pratik-mahalle pratik-mahalle pratik-mahalle left review comments

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /