Extract CSV, with field delimiter consistent with the schema used

Please replace this line with full information about your idea or problem. If it’s a bug share as much as possible to reproduce it.

I have this input CSV file:

fieldNameA;fieldNameB
0123;c

If I run extract the field delimiter is changed from ; to ,:

fieldNameA,fieldNameB
123,c

I think that the default way should be to have the output field separator as the one of the input.

Moreover if I have this schema, in which I set delimiter: ;

path: input.csv
name: input
profile: tabular-data-resource
scheme: file
format: csv
hashing: md5
encoding: utf-8
dialect:
  delimiter: ;
schema:
  fields:
    - type: integer
      name: fieldNameA
    - type: string
      name: fieldNameB

and then run frictionless extract input.yml --csv, I have again , as field separator and it’s inconsistent with the schema I have.

fieldNameA,fieldNameB
123,c

I think that if I use a schema, I should have a consistent output also for delimiter setting. This is related to this discussion.

Thank you

[lwinfree]

@aborruso I’m actually going to move this issue to the frictionless-py repo, since it is about that code. (Just FYI!)

[roll]

@aborruso The v5 changes have not affected it so I’ll prioritize this now