We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The current document has lots of maxxxxx and minxxxx properties, using the property names to link them together.
maxxxxx
minxxxx
resources: compute: - name: "compute-001" type: "https://www.purl.org/ivoa.net/resource-types/generic-compute" spec: mincores: 8 maxcores: 16 minmemory: 16 maxmemory: 32
This means each class object has lots of top level minxxx and maxxxx properties associated with it, cluttering up the class interface.
minxxx
maxxxx
It is better to define maximum and minimum properties as a re-useable element that contains the min and max values as a pair.
min
max
resources: compute: - name: "compute-001" type: "https://www.purl.org/ivoa.net/resource-types/generic-compute" spec: cores: min: 8 max: 16 memory: min: 16 max: 32
It cleans up the class interfaces and enables us to automate some validation that checks that the max value is always greater than the min value.
The text was updated successfully, but these errors were encountered:
Added min/max pairs ivoa-std#47
48c8d22
Fixed in #60
Sorry, something went wrong.
Zarquan
No branches or pull requests
The current document has lots of
maxxxxx
andminxxxx
properties, using the property names to link them together.This means each class object has lots of top level
minxxx
andmaxxxx
properties associated with it, cluttering up the class interface.It is better to define maximum and minimum properties as a re-useable element that contains the
min
andmax
values as a pair.It cleans up the class interfaces and enables us to automate some validation that checks that the max value is always greater than the min value.
The text was updated successfully, but these errors were encountered: