-
Notifications
You must be signed in to change notification settings - Fork 130
Use version number placeholders in content #220
Comments
Happy to work on that, if the WG members agree. |
Yeah, plan was to do this from the start, except it would read an external json when available, and default to a local one for testing. |
Exactly, a JSON should be enough to hold the versions and their string/URL representations. |
+1 to this. Feel free to PR @AntouanK |
@therebelrobot I have an open PR for that |
👍 really useful |
See #251 for some movement on this |
#251 fixed the version number issue. We didn't do node version numbers yet, but we can just do that when a release comes out from there, or if someone wants to spend a few minutes doing it. |
I thought I closed this a long time ago. Good call. Looks like @Fishrock123 and I are both doing some spring cleaning today. Perhaps our differing sort options are keeping us from bumping in to each other's issue closings ;) |
After just pushing #219, can we please add placeholders in the content files for:
Those should be replaced during the build process, so we don't need to touch every single translation, updating every single download link for each platform with a new release.
The text was updated successfully, but these errors were encountered: