field names in modules.json about magisk-modules-repo-util HOT 4 CLOSED

Yes, full ack to that. I just try to evaluate possibilities. Looking from the users' perspective, this is technically correct – but if the client maintainer cannot "quickly implement" it – and MRepo lacks some functionality they need which "the other" has… I could e.g. have my magisk-repo class export a modules.json in the format used by other clients, to mitigate for a while. But yes, that could lead to either not working anyway (different ZIP than expected) – or to the maintainers of those other clients to see no urgency 🤷‍♂️

That said, it would be nice to have a (base) standard to agree upon. But if that's not possible, we'll have to accept that. I lack the deep insight to tell or argue here, so I'll accept your decision 😄

from magisk-modules-repo-util.

Since there never was an official json format, I uses a scheme which I like, I don't think modules.json of the Magisk-Alt-Repo is a good choice, the zip they use is not a real magisk module.

from magisk-modules-repo-util.

OK, thanks! So you think even if we made the format of the JSON "compatible", it won't work anyway (as we'd ship a "real module" in the ZIP)?

from magisk-modules-repo-util.

It shouldn't be up to repositories to adapt clients, this should be done by clients.

from magisk-modules-repo-util.