issue_comments

Ok thanks for the recommandations.

I'm thinking of using this kind of class to handle object creation:

```python import xarray as xr import motion

class Analogs: def new(cls, ...): array = xr.DataArray(...) cls.verify(array) return array

@staticmethod
def verify(array):
    print("verification...")

@classmethod
def from_csv(cls, filename:str, ...):
    array = xr.DataArray(filename, ...)
    cls.verify(array)
    return array

```

Let's say I define another Markers class for another type of data. Is it possible that my accessor exposes different functions according to class e, g:

```python @xr.register_dataarray_accessor("foo") class DataArrayAccessor(object): def init(self, xarray_obj: xr.DataArray): self._obj = xarray_obj

def to_csv(self):
    """
    This function is exposed to all objects
    but behave differently if it is a Markers or an Analogs
    """

def marker_only_function(self):
    """
    This function is only exposed to 
    array created with the Marker class
    """

def analog_only_function(self):
    """
    This function is only exposed to
    array created with the Analog class
    """

```

My ultimate goal is to have this kind of API:

python analogs = ( Analogs.from_csv("filename.csv") .foo.center() # foo accessor generic method .foo.rectify() # foo accessor specific method for Analogs object .mean() # xarray method )

Is it because you would need a hook that is triggered by DataArray. init

Yes, I need to test some properties when creating the DataArray such as shape and dimensions properties.

Why can't you initialise whatever you need to upon first access?

How do you do that?