fix(GCI82): fix rule to handle record types and adjust test cases (#104)#105
Open
vimarie wants to merge 1 commit into
Open
fix(GCI82): fix rule to handle record types and adjust test cases (#104)#105vimarie wants to merge 1 commit into
vimarie wants to merge 1 commit into
Conversation
MP-Aubay
requested changes
May 21, 2025
cali0pe
force-pushed
the
fix/challenge25-GCI82-manage-record
branch
from
b623c94 to
50ea70a
Compare
utarwyn
reviewed
May 31, 2025
Member
utarwyn
left a comment
utarwyn
left a comment
There was a problem hiding this comment.
Can you correct the conflict in the CHANGELOG file?
After this, I think we will good to go 🚀 Thank you for the contribution!
cali0pe
force-pushed
the
fix/challenge25-GCI82-manage-record
branch
from
b5483a1 to
4618de8
Compare
|
This PR has been automatically marked as stale because it has no activity for 30 days. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR resolves the issue #104