Skip to content
New issue

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

Incompatible with Symphony 3 #423

Closed
BramDriesen opened this issue Dec 1, 2017 · 7 comments
Closed

Incompatible with Symphony 3 #423

BramDriesen opened this issue Dec 1, 2017 · 7 comments
Labels
Milestone

Comments

@BramDriesen
Copy link

When being upgraded to Symphony 3. DrupalExtension becomes incompatible because of the use of plain scalars without quoting them.

The file ".../behat/vendor/drupal/drupal-extension/src/Drupal/DrupalExtension/ServiceContainer/config/services.yml" does not contain valid YAML.

The reserved indicator "%" cannot start a plain scalar; you need to quote the scalar at line 34 (near "class: %drupal.drupal.class%").

jhedstrom added a commit that referenced this issue Dec 1, 2017
#423 Quoted all usages of '%' in the YAML files
jhedstrom added a commit that referenced this issue Dec 1, 2017
#423 Quoted all usages of '%' in the YAML files

Signed-off-by: Jonathan Hedstrom <jhedstrom@gmail.com>
@jhedstrom
Copy link
Owner

Thanks again!

@jhedstrom jhedstrom added this to the 4.0 release milestone Dec 1, 2017
@jhedstrom jhedstrom added the bug label Dec 1, 2017
@alexfinnarn
Copy link

I'd like to see this issue reopened due to https://github.com/jhedstrom/drupalextension/blob/master/src/Drupal/DrupalExtension/ServiceContainer/config/services.yml#L49 and potentially other places in the code.

I just switched to "drupal/drupal-extension": "dev-master" via Composer and got the same error as above.

@jhedstrom
Copy link
Owner

Is this resolved with your PR in #439 now?

@jhedstrom jhedstrom reopened this Dec 6, 2017
@alexfinnarn
Copy link

@jhedstrom it does appear to fix my issue, thanks!

I'm not sure if contributors are remembering to add quotes though and if my issue is caused by added code since the previous commits. I don't know if you can make that more explicit when adding/reviewing code or add a test that would point out invalid YAML according to...I don't really know what validates the YAML.

You can close for now or try another find and replace for other non-quoted strings.

@jhedstrom
Copy link
Owner

@alexfinnarn to prevent it from regressing in the future, I suppose we should be testing against symfony 3 (although we do test against Drupal 8.4, which uses symfony 3, so I'm not sure what else is to be done)...

@alexfinnarn
Copy link

Makes sense. Can you try adding that to the matrix somehow? I'm surprised it works in Drupal 8 but not in my case...I'm trying this on a Drupal 7 site though so no composer install of Drupal's codebase for me.

@jhedstrom
Copy link
Owner

I've opened #442 so we don't lose track of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants