Skip to content

fix:: applies pattern of c_double_quoted to provide c_single_quoted, … - #70

Closed
bart-at-qqdatafruits wants to merge 1 commit into
moosetechnology:developmentfrom
bart-at-qqdatafruits:development
Closed

fix:: applies pattern of c_double_quoted to provide c_single_quoted, …#70
bart-at-qqdatafruits wants to merge 1 commit into
moosetechnology:developmentfrom
bart-at-qqdatafruits:development

Conversation

@bart-at-qqdatafruits

Copy link
Copy Markdown

applies pattern of c_double_quoted to provide c_single_quoted, uncommented in c_flow_json_content in occordence to https://yaml.org/spec/1.2.2/#rule-c-flow-json-content as shared missing in #66

@Ducasse

Ducasse commented Jan 21, 2026

Copy link
Copy Markdown
Contributor

Hi bart
Thanks for your contribution.
I do not know who is maintaining petit parser nowadays.
So let us wait if there are some reactions.
S.

@bart-at-qqdatafruits

Copy link
Copy Markdown
Author

Hi bart Thanks for your contribution. I do not know who is maintaining petit parser nowadays. So let us wait if there are some reactions. S.

Hi Stéphane

I don't understand all the formatting changes, if you have some pointers on that (avoiding them if possible) as they mask the real intended edits.

Thanks in advance,
Bart,

@jecisc

jecisc commented Jan 22, 2026

Copy link
Copy Markdown
Member

This is due to a change of the Tonel export format in Pharo 12.

Some info here: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/ExportFormats.md#tonel-versions

@Ducasse

Ducasse commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Tx cyril! You were fast :)

@bart-at-qqdatafruits

Copy link
Copy Markdown
Author

I suggest to replace with pull request 71 #71

@bart-at-qqdatafruits

Copy link
Copy Markdown
Author

This is due to a change of the Tonel export format in Pharo 12.

Some info here: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/ExportFormats.md#tonel-versions

I tried to improve in #71
There, I put the update .profile in the root folder and updated the one in the src folder, I think the file should be in the root folder but am unsure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants