You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The list in this repository is based on the README.md in the awesome-gbdev, but a lot of custom elements are added, such as the video players, the "info" message about the disambiguation GB/GBA etc...
We would need some way to template the base list and "render" it into this way, possibly with commented lines so the one in the awesome-gbdev remains clean (this pontential solution is mentioned in gbdev/awesome-gbdev#203)
The Markdown could be parsed into a list of lists (categories of entries), and that processed somehow. Replacements like "insert this between category X and Y", "process entry E thusly", etc.
The Markdown could be parsed into a list of lists (categories of entries), and that processed somehow. Replacements like "insert this between category X and Y", "process entry E thusly", etc.
It's an interesting proposal, thanks ISSO. For sure better than keeping unrelated code in the source list (even if commented).
Considering our list is linted by awesome-lint (actually our version of it: https://github.com/gbdev/list-linter) it's already consistent to the point we could do that, but there's still a lot of spare and custom text around that would make it fail.
I'd suggest trying to go at it anyway, and seeing what hurdles come up. It may be possible to simply ignore these elements, pass them through without any processing, or give them some special treatment as with the rest, for example.
I'd suggest trying to go at it anyway, and seeing what hurdles come up. It may be possible to simply ignore these elements, pass them through without any processing, or give them some special treatment as with the rest, for example.
Ok, but it would be super low priority for me, as manually merging the list is not a big deal anyway and it happens once(maybe twice) a year. Ping me if you have time for tests
Activity
[-]Automatize the merge from the List[/-][+]Automate the merge from the List[/+]ISSOtm commentedon Jan 5, 2022
What needs to be done?
avivace commentedon Jan 6, 2022
The list in this repository is based on the README.md in the awesome-gbdev, but a lot of custom elements are added, such as the video players, the "info" message about the disambiguation GB/GBA etc...
We would need some way to template the base list and "render" it into this way, possibly with commented lines so the one in the awesome-gbdev remains clean (this pontential solution is mentioned in gbdev/awesome-gbdev#203)
ISSOtm commentedon Jan 6, 2022
The Markdown could be parsed into a list of lists (categories of entries), and that processed somehow. Replacements like "insert this between category X and Y", "process entry E thusly", etc.
avivace commentedon Jan 6, 2022
It's an interesting proposal, thanks ISSO. For sure better than keeping unrelated code in the source list (even if commented).
Considering our list is linted by awesome-lint (actually our version of it: https://github.com/gbdev/list-linter) it's already consistent to the point we could do that, but there's still a lot of spare and custom text around that would make it fail.
ISSOtm commentedon Jan 6, 2022
I'd suggest trying to go at it anyway, and seeing what hurdles come up. It may be possible to simply ignore these elements, pass them through without any processing, or give them some special treatment as with the rest, for example.
avivace commentedon Jan 8, 2022
Ok, but it would be super low priority for me, as manually merging the list is not a big deal anyway and it happens once(maybe twice) a year. Ping me if you have time for tests
ci, docs: rebuild on awesome-gbdev changes, add CONTRIBUTING.md (#8)