RailcraftPackUpdater issueshttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues2017-05-13T21:09:59Zhttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/2Unit Tests2017-05-13T21:09:59ZLizzyUnit Testshttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/3Updater for the updater2017-06-12T13:43:49ZLizzyUpdater for the updaterUpdate the updater, so you can update while you update.
Perhaps only run if a 'telemetry' config value is set?
Will possibly require another "app" that runs before the main updater to update it (yo dawg...)Update the updater, so you can update while you update.
Perhaps only run if a 'telemetry' config value is set?
Will possibly require another "app" that runs before the main updater to update it (yo dawg...)v1.3 - Automation!LizzyLizzyhttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/6Automate builds/releases2017-06-10T23:56:57ZLizzyAutomate builds/releasesCurrently, builds have to be packaged up manually. This is inefficient.
- [ ] Windows builds
- [ ] Linux builds
- [ ] Mac buildsCurrently, builds have to be packaged up manually. This is inefficient.
- [ ] Windows builds
- [ ] Linux builds
- [ ] Mac buildsv1.3 - Automation!LizzyLizzyhttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/7GUI elements2017-06-12T13:44:09ZLizzyGUI elementstry using small gui boxes to ask for client id, secret, optional mods and whether they want to keep the update checker ontry using small gui boxes to ask for client id, secret, optional mods and whether they want to keep the update checker onv1.3 - Automation!LizzyLizzyhttps://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/11package up MultiMC-importable instance zip2017-06-10T23:56:56ZLizzypackage up MultiMC-importable instance zipThis should allow for easy setups of new multimc instances. It will contain no mods, configs or any other MC stuff apart from the Forge build details and the updater.
The updater's config should not need to be edited manually as it will ...This should allow for easy setups of new multimc instances. It will contain no mods, configs or any other MC stuff apart from the Forge build details and the updater.
The updater's config should not need to be edited manually as it will be generated if it's not present (requires #9) and details for ClientID/Secret and Optional Mods should be obtained via a small GUI (#7).
may also only need to be released once as self-updating of the updater (#6 may help with that).
This is not an urgent project.https://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/12JSONDecodeError2017-08-05T18:06:40ZMartinJSONDecodeError```
Traceback (most recent call last):
File "main.py", line 135, in <module>
File "main.py", line 30, in justDoIt
File "main.py", line 70, in getDownloadInfo
File "site-packages\requests\models.py", line 885, in json
File "json...```
Traceback (most recent call last):
File "main.py", line 135, in <module>
File "main.py", line 30, in justDoIt
File "main.py", line 70, in getDownloadInfo
File "site-packages\requests\models.py", line 885, in json
File "json\__init__.py", line 319, in loads
File "json\decoder.py", line 339, in decode
File "json\decoder.py", line 357, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
```
This is likely because the last pack update was a minor update, which I've never submitted before.https://gitlab.theender.net/Lizzy/RailcraftPackUpdater/-/issues/13Upcoming API changes2017-10-31T12:54:30ZMartinUpcoming API changesThe API urls need to be changed from `example.org/api/endpoint` to `example.org/api/v1/endpoint`
In the future, if major non-bug fix changes and/or additions occur it will result in a copy of the API being put in a `v2` sub directory. T...The API urls need to be changed from `example.org/api/endpoint` to `example.org/api/v1/endpoint`
In the future, if major non-bug fix changes and/or additions occur it will result in a copy of the API being put in a `v2` sub directory. The old version will remain for backwards-compatibility, but to access new features the client will need to be updated to point to the v2 (or higher depending on the number of prior versions) directory.
For now the old location will continue working, but once this client has been updated the old links will be removed and all usages of the `api_version` field will be purged from the API, along with the `version` endpoint which only provides this field.