-
Notifications
You must be signed in to change notification settings - Fork 27
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
Amend group-name parser to avoid forbidden forge-string characters #35
Comments
I think that's something that you can work on, @dhananjaya93. Just check all group names and turn any symbols other than |
Got it. I will start working on it.
Best ,
Dhananjaya
…On Wed, 1 Dec, 2021, 5:16 pm Stephan Schiffels, ***@***.***> wrote:
I think that's something that you can work on, @dhananjaya93
<https://github.com/dhananjaya93>. Just check all group names and turn
any symbols other than _, -, . or alphanumeric into underscores.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWAV3NM6BMAD7TN3JD5ZA4DUOZC6VANCNFSM5HXWNQQA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I checked the all the group names and identified the characters to replace. I can replace them but how can I change the individual packages that already exist? Do I need to update all the .janno files of existing packages? |
I guess these issues are not present in every package, right? If so, then it would boil down to writing a script that loops through the package folders, replaces the .janno files and updates the POSEIDON.yml files ( |
Well, we could parse them in Haskell using a parser that only allows a certain alphabet. That would then automatically complain. Though it would be a pretty brutal move. |
I like it. Better a painful but clear error message than obscure failures with specific sub-commands, right? |
OK, I just renamed this issue to make the pending ToDo clearer. |
Some of the group names that we've imported from the AADR contain symbols like
<
or others that trip up our parsing of forge strings.Ideally we should have group names following alphanumeric symbols and
_
and-
and.
or so, but not anything more exotic.The text was updated successfully, but these errors were encountered: