Skip to content

Ensure config blocks are consistent #2 #17156

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

Closed
wants to merge 3 commits into from

Conversation

HeahDude
Copy link
Contributor

Continuation of #16992.

@carsonbot carsonbot added this to the 4.4 milestone Aug 11, 2022
parameters:
env(AUTH_FILE): '../config/auth.json'
google:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to be more generic in these examples.

@HeahDude
Copy link
Contributor Author

I need to check and fix some reported errors.

Status: needs work

</security:config>
</container>
</config>
</srv:container>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it worth dealing with this error: The child node "firewalls" at path "security" must be configured.?

A way to be consistent here would be to add a <!-- ... --> at the beginning of the <config> node, ad done already in others places.

But that wouldn't fix the error because of the required config schema, unless we expand it to something like:

<firewall name="main">
    <!-- ... -->
</firewall>

(same for other formats)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with a consistent config without trying to fix a false positive from the checker.

@javiereguiluz
Copy link
Member

@HeahDude do you still consider this as "needs work" or is it ready? Thanks!

@HeahDude
Copy link
Contributor Author

HeahDude commented Oct 5, 2022

Yes, sadly it still needs work, and I need help, I'll see if I can get some next week at the Forum PHP when meeting old friends :).

@HeahDude
Copy link
Contributor Author

Thanks for the review @wouterj :), I'll work on it later this week.

@javiereguiluz
Copy link
Member

Symfony 4.4 is no longer supported ... so we should rebase this PR to 5.4 or higher. Thanks!

@javiereguiluz
Copy link
Member

It's sad to see that this PR stalled. @HeahDude would you have the time and energy needed to rebase it? If you don't, we totally understand it. Thanks!

@HeahDude
Copy link
Contributor Author

@javiereguiluz Yes, thanks for the ping :)

@OskarStark
Copy link
Contributor

Again, asking friendly to retarget on 5.4 😍

Thanks!

@OskarStark OskarStark modified the milestones: 4.4, 5.4 Aug 14, 2023
@wouterj
Copy link
Member

wouterj commented Feb 19, 2024

I'm afraid we'll have to close this. If you ever find time to continue this great (in both definitions of the word) contribution, we can always reopen it.

@wouterj wouterj closed this Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants