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
Type of issue
technical debt
Description of issue
In ocibundle.tools there is a pattern like:
type Rootfs string func (r Rootfs) Path()
Where the value of the Rootfs string itself is the bundle path, and Rootfs.Path() gives the rootfs path inside that bundle.
This is very confusing from the point of view of type naming etc.
At point of use it is slightly better... Rootfs("mybundle").Path() being possible to read as give me Path of the Rootfs of "mybundle".
Rootfs("mybundle").Path()
Path
Rootfs
"mybundle"
We should consider deprecating and replacing with nicer named functions on a single bundle type / struct.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Type of issue
technical debt
Description of issue
In ocibundle.tools there is a pattern like:
Where the value of the Rootfs string itself is the bundle path, and Rootfs.Path() gives the rootfs path inside that bundle.
This is very confusing from the point of view of type naming etc.
At point of use it is slightly better...
Rootfs("mybundle").Path()
being possible to read as give mePath
of theRootfs
of"mybundle"
.We should consider deprecating and replacing with nicer named functions on a single bundle type / struct.
The text was updated successfully, but these errors were encountered: