entry_to_string function implemented

[KlowdfurrRad]

Implemented entry_to_string function.
Wrote 3-4 simple tests for it.
Wrote documentation for entry_to_string in /include/stumpless/entry.h

Let me know what changes I should make.

#448

[codecov]

Codecov Report

Attention: Patch coverage is 85.00000% with 9 lines in your changes missing coverage. Please review.

Project coverage is 90.51%. Comparing base (1d2df58) to head (34783a7).

Files with missing lines	Patch %	Lines
src/entry.c	85.00%	7 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           latest     #465      +/-   ##
==========================================
- Coverage   90.59%   90.51%   -0.08%     
==========================================
  Files          47       47              
  Lines        4379     4439      +60     
  Branches      587      594       +7     
==========================================
+ Hits         3967     4018      +51     
- Misses        279      286       +7     
- Partials      133      135       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[goatshriek]

Checking in to see if you plan to continue work on this, per the project's inactivity policy. Resolving the CI failures is a good next step.

[KlowdfurrRad]

Checking in to see if you plan to continue work on this, per the project's inactivity policy. Resolving the CI failures is a good next step.

Hey, sorry.
Do you have any idea where I can start to resolve the CI failures ? I am not very familiar with CI.

[goatshriek]

The CI runs (GitHub Actions in this case) are essentially just scripts that are run to run tests, examples, and perform other checks on the code. You can look into the .github/workflows folder for their definitions.

It's been long enough that the logs from the failed runs have aged off. I recommend you run the tests locally on your own machine to see what is failing, and then fix that. You can look at the test documentation for instructions on building and running the tests, or just copy what the GitHub Action does.

[KlowdfurrRad]

The CI runs (GitHub Actions in this case) are essentially just scripts that are run to run tests, examples, and perform other checks on the code. You can look into the .github/workflows folder for their definitions.

It's been long enough that the logs from the failed runs have aged off. I recommend you run the tests locally on your own machine to see what is failing, and then fix that. You can look at the test documentation for instructions on building and running the tests, or just copy what the GitHub Action does.

Thank you ! I will take a look at this again soon , I hope :/. My semester is packed but I do want to try working on code like this!