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
I see now at least 2 events in beginning of Dec... would be nice if you could push soon a new version (which just includes the latest events).
( I think it would at least appear automatic in f-droid, not sure about g-play )
thanks for considering.
Also, long-therm i would suggest to split the "app" and the "data" into 2 repos.
the data (res/raw/menu.json) could then be refresh-loaded by the app separately (maybe even from the master repo raw.github.org :) )
also the data could be included (there some gradle receipts) to be included if build a new version
for the data-repo, there could run some custom .travis checks for to prove pull-requests. (are the urls accessible, is the .ics file a valid one, check the format (json-schema-validation), ... )
The text was updated successfully, but these errors were encountered:
Hrm, menu.json is loaded from a webserver so already released separately from Giggity itself, exactly for reasons like this.. It's been like that from the start, I never wanted to have to do releases just for getting a new event into the menu.
I see now at least 2 events in beginning of Dec... would be nice if you could push soon a new version (which just includes the latest events).
( I think it would at least appear automatic in f-droid, not sure about g-play )
thanks for considering.
Also, long-therm i would suggest to split the "app" and the "data" into 2 repos.
for the data-repo, there could run some custom .travis checks for to prove pull-requests. (are the urls accessible, is the .ics file a valid one, check the format (json-schema-validation), ... )
The text was updated successfully, but these errors were encountered: