Fix for taking in account spaces inside numlignepublic #1
Conversation
This file contains 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
added 2 commits
February 17, 2024 13:42
… for Citadine 1 and 2)
… for Citadine 1 and 2) + Removed ;
|
P.S.: J'ai oublié mais il faudra également passer en version 1.1.5 |
|
Hey Théo, |
De rien ;) Parfait, merci beaucoup ! |
maelgangloff
approved these changes
Feb 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey, is it possible to merge this pr as it fixes Citadine 1 and Citadine 2 stops getting
Bonjour, pouvez-vous merge cette pr afin de résoudre le bug sur les citadine 1 et 2, le numlignepublic contient un espace et donc la regex ne fonctionnait pas