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
Is your feature request related to a problem? Please describe.
Infrared does currently have a simple REST-API but it's missing 2 core features: listing all currently active configs as well as retreiving a sample config.
Describe the solution you'd like
Implement 2 new API routes, preferably GET /proxies for retreiving all currently active proxies and GET /proxies/{fileName} for retreiving the contents of a specific config file.
Describe alternatives you've considered
I have made my way around this issue by simply reading the contents of the config directory and parsing all contents of these files into one bis JSON array. But there are wayyy more points of failure in this rather than doing this by the built-in REST API.
The text was updated successfully, but these errors were encountered:
After a bit of trial an error I got the rewrite working on my system and the API does all it's supposed to.
But more documentation would be much appreciated in the future (e. g. that you need to pass the config file content as a JSON object).
I just have one more question: Can I pass the forge/fabric compatibility to the requesting client?
I have a few modded servers which all show Incompatible Vanilla server with the Better Compatibility Checker.
Passing the corresponding versionName and/or protocolNumber does not seem to do anything.
Is your feature request related to a problem? Please describe.
Infrared does currently have a simple REST-API but it's missing 2 core features: listing all currently active configs as well as retreiving a sample config.
Describe the solution you'd like
Implement 2 new API routes, preferably
GET /proxies
for retreiving all currently active proxies andGET /proxies/{fileName}
for retreiving the contents of a specific config file.Describe alternatives you've considered
I have made my way around this issue by simply reading the contents of the config directory and parsing all contents of these files into one bis JSON array. But there are wayyy more points of failure in this rather than doing this by the built-in REST API.
The text was updated successfully, but these errors were encountered: