Compatibility with multi-page plans

[3liFi]

Only the first page of the table seems to be processed properly. All the substitutions belonging to the page circled in green show up, the red ones do not.

.

The result of getAllData()

[pixelcmtd]

That's actually on purpose, because all timetable JSONs I ever had the chance of looking at didn't have multiple Childs.
For example, using the public credentials (accemus -j 187801 public | jq .):

[
  {
    "Id": "c9fb6314-cda8-4c4c-93fe-328580dc3502",
    "Date": "31.03.2020 17:18",
    "Title": "Homeschooling-Stundenplan",
    "Detail": "",
    "Tags": "",
    "ConType": 2,
    "Prio": 0,
    "Index": 0,
    "Childs": [
      {
        "Id": "c9fb6314-cda8-4c4c-93fe-328580dc3502_76",
        "Date": "31.03.2020 17:18",
        "Title": "Homeschooling-Stundenplan",
        "Detail": "https://light.dsbcontrol.de/DSBlightWebsite/Data/13ccccbb-e6a8-466a-addc-00bba830c6cf/c9fb6314-cda8-4c4c-93fe-328580dc3502/c9fb6314-cda8-4c4c-93fe-328580dc3502_000.jpg",
        "Tags": "",
        "ConType": 4,
        "Prio": 0,
        "Index": 76,
        "Childs": [],
        "Preview": "13ccccbb-e6a8-466a-addc-00bba830c6cf/c9fb6314-cda8-4c4c-93fe-328580dc3502/c9fb6314-cda8-4c4c-93fe-328580dc3502_000.jpg"
      }
    ],
    "Preview": ""
  }
]

The same holds true for GymPeg plans: The elements of the outer list represent plans, the Childs just consists of one element containing all the actually relevant information.

Could you please outline, how yours looks? Are the Childs plans now? What are the outer elements?

[3liFi]

Hmm, I see. In my case the outer Element also represents a plan, while the Childs hold all the data. However the data is spread out over numerous Child elements. Every Child represents one page of the plan. I guess in my case it would be necessary for this function to not only use p['Childs'][0], but every element in p['Childs']; something like p['Childs'][i], where i iterates through all Childs.

Iterable<DownloadingPlan> downloadPlans(
    List json, {
    bool downloadPreviews = false,
  }) =>
      json.map((p) => p['Childs'][0]).map((p) => DownloadingPlan(
          p['Detail'],
          p['Preview'],
          http.get(p['Detail'],
              ttl: Duration(days: 4),
              defaultCharset: (x) => String.fromCharCodes(x)),
          downloadPreviews
              ? http.getBin('$previewEndpoint/${p['Preview']}')
              : null));

The login info I used is generally considered public, so if you want to replicate it yourself: username: "152321" password: "krsmrz21".

[pixelcmtd]

Ok, I think I understand everything now. 7.1.1 mitigates this by making every "page" its own Plan. While this is not the right behavior, it overcomes the biggest problem, missing data, without breaking the API. A good fix will take a while. Also: Your plans, despite being Untis 2021, are very differently formatted than any other plans I have ever seen. I already have an idea for making the plan parser work.

By the way: Another interesting problem is the info field at the top of the first page of these plans. I hope, I can also get parser support for them working as well.

[pixelcmtd]

#13 is now concerned with extending the compatibility across different orderings.