#Preview of some routes currently: <https
1 messages · Page 1 of 1 (latest)
what kind of feedback are you looking for specifically?
any and all.
- is there anything that's missing that you want to see in existing endpoints?
- are there any endpoints that would be helpful to you?
will “supportEnds” ever be used..?
in the future yes; old versions won't have it filled
Also for javadocs is that something planned for a later version?
soon (tm)
also, no namespaces anymore?
someone deleted a message
I did to join the thread
Because that's how you do it on mobile, literally no other way
hola
might make sense to split up the java version into minimum and recommended?
It's just the requirement currently; what is the use-case for "recommended" Java version?
It's the highest that version supports
I.e. if it's held back by ASM or jline or whatever
So we would need to be able to update it
But that def was something people asked about before, can I use java 21 with 1.19
.
unsure how I want to do that currently
v3 is delayed until Cloudflare fixes something
I'm going to hell
query {
project(name: "paper") {
name
versions(latest: true) {
nodes {
name
java {
version {
minimum
}
flags {
recommended
}
}
builds(channel: DEFAULT, latest: true) {
nodes {
number
channel
downloads(name: "server") {
id
name
sha256
size
url
}
}
}
}
}
}
}
{
"data": {
"project": {
"name": "paper",
"versions": {
"nodes": [
{
"name": "1.21.1",
"java": {
"version": {
"minimum": 21
},
"flags": {
"recommended": [
"-XX:+AlwaysPreTouch",
"-XX:+DisableExplicitGC",
"-XX:+ParallelRefProcEnabled",
"-XX:+PerfDisableSharedMem",
"-XX:+UnlockExperimentalVMOptions",
"-XX:+UseG1GC",
"-XX:G1HeapRegionSize=8M",
"-XX:G1HeapWastePercent=5",
"-XX:G1MaxNewSizePercent=40",
"-XX:G1MixedGCCountTarget=4",
"-XX:G1MixedGCLiveThresholdPercent=90",
"-XX:G1NewSizePercent=30",
"-XX:G1RSetUpdatingPauseTimePercent=5",
"-XX:G1ReservePercent=20",
"-XX:InitiatingHeapOccupancyPercent=15",
"-XX:MaxGCPauseMillis=200",
"-XX:MaxTenuringThreshold=1",
"-XX:SurvivorRatio=32"
]
}
},
"builds": {
"nodes": [
{
"number": 10,
"channel": "DEFAULT",
"downloads": [
{
"id": "server",
"name": "paper-1.21.1-10.jar",
"sha256": "c49d951314cad0a3c0572ba762de324fd537a2a24a75c965f9d80daea3e3da10",
"size": 49055524,
"url": "http://localhost:8080/c49d951314cad0a3c0572ba762de324fd537a2a24a75c965f9d80daea3e3da10/paper-1.21.1-10.jar"
}
]
}
]
}
}
]
}
}
}
}
1 query vs many, with filtering support
we love gql
I don't hate it honestly
I read your mind, your dreams have been fulfilled
hangar had a fun POC where I transformed gql into sql
heh
I started working on it maybe an hour ago and it's fully working, just not with all fields currently
the reason for it is some URLs started to look weird when implementing filtering
ex: /v3/projects/paper/versions/1.21.1?channel=DEFAULT&latest=true
those params don't make sense for that endpoint, so I added a /1.21.1/builds endpoint, but then lots of duplication
and so on
valid
I might actually spend more time looking into GraphQL - if you have any thoughts there, feel free to let me know
it's honestly been forever since i've touched it - all i remember is the distaste i felt trying to get it working lol
this was like a good ~5 years ago
I like GQL for some APIs
It's really nice for realtime integrations since you can do it easily over websockets
wheee
query {
project(name: "paper") {
name
versions(filterBy: {status: SUPPORTED}) {
name
builds(last: 1) {
number
}
}
}
}
{
"data": {
"project": {
"name": "paper",
"versions": [
{
"name": "1.21.1",
"builds": [
{
"number": 10
}
]
}
]
}
}
}
@barren robin write the gradle plugin for me