JuliaDataCubes / JuliaDataCubes/YAXArrays.jl

savecube should add file extension based on backend if it is not present

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
132
Forks
25
PR merge metrics
No merged PRs in 30d

Description

When the file extension on the path is not given, savecubecould add the proper extension based on the backend, and it could also check for proper extension use. This could be done by adding a ext key into the backenddictionary.
I thought this was the case and got bitten, because the savecube with netcdf tried to overwrite the zarr file.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the savecube entry point and locate the backend dictionary described in the issue. Review how NetCDF and Zarr paths are handled, then verify that an omitted extension is inferred from the backend and that an incompatible extension is detected rather than allowing the wrong file to be overwritten.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.