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

API Remove configuration of _resources path #56

Conversation

GuySartorelli
Copy link
Member

NOTE This will need to be targetted at 2 once that branch has been created (see silverstripe/silverstripe-framework#10349)

BC breaking changes

  • Removed Library::DEFAULT_RESOURCES_DIR
  • Set Library::RESOURCES_PATH to explicitly be "_resources"
  • Removed Library::getResourcesDir()

Parent issue

@michalkleiner
Copy link
Contributor

Why would we remove the configurability of this and not just change the default?

@GuySartorelli
Copy link
Member Author

GuySartorelli commented Aug 3, 2022

That's what the issue is for, but I realised that after doing the work. The configuration feels a bit like tech debt to me but have asked for clarification of the intent.

@michalkleiner
Copy link
Contributor

I reckon once it was made configurable it feels wrong to force users into something opinionated again, so I would vote for changing the default to _resources so it's consistent with what some other modules had configured, but leave it configurable so that devs can still leverage that in project code if they wanted to. I imagine not everyone is using _resources, might be using something custom and have other systems/URLs etc depending on it.

@GuySartorelli
Copy link
Member Author

Closed in favor of #57

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.

2 participants