Skip to content
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

Open
stschiff opened this issue Nov 10, 2021 · 8 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@stschiff
Copy link
Member

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.

@stschiff stschiff added the bug Something isn't working label Dec 1, 2021
@stschiff
Copy link
Member Author

stschiff commented Dec 1, 2021

I think that's something that you can work on, @dhananjaya93. Just check all group names and turn any symbols other than _, -, . or alphanumeric into underscores.

@dhananjaya93
Copy link
Contributor

dhananjaya93 commented Dec 2, 2021 via email

@dhananjaya93
Copy link
Contributor

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?

@nevrome
Copy link
Member

nevrome commented Dec 7, 2021

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 (trident update).

@nevrome
Copy link
Member

nevrome commented Jul 26, 2023

@AyGhal and I have fixed the problematic groups that existed now in #132.

Another question is, whether we should introduce some mechanism to prevent the creation of packages with such "broken" group names. This could be a future feature of trident.

@stschiff
Copy link
Member Author

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.

@nevrome
Copy link
Member

nevrome commented Aug 14, 2023

I like it. Better a painful but clear error message than obscure failures with specific sub-commands, right?

@stschiff stschiff changed the title Problematic group names Amend group-name parser to avoid forbidden forge-string characters Aug 14, 2023
@stschiff
Copy link
Member Author

OK, I just renamed this issue to make the pending ToDo clearer.

@stschiff stschiff self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants