| Commit-Queue | +1 |
PTAL. WDYT?
I am also wondering if we should rename `SeDefaultResource()` to `SetRootResource()` for more clarity. Although this would create quite some churn,I think the name would be less confusing and more disassociated with the current name.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
PTAL. WDYT?
I am also wondering if we should rename `SeDefaultResource()` to `SetRootResource()` for more clarity. Although this would create quite some churn,I think the name would be less confusing and more disassociated with the current name.
I was going to say that this change could be a bit confusing, because we've been calling `SetDefaultResource()` deprecated/discouraging it in reviews for so long. Renaming SGTM although I agree it will create quite a lot of churn.
source->SetDefaultResource(default_resource);Remove duplicate call?
// We intentionally do not use `SetDefaultResource` here as we do not want to
// serve index.html for non-HTML paths.Comment needs to be updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Rebekah PotterPTAL. WDYT?
I am also wondering if we should rename `SeDefaultResource()` to `SetRootResource()` for more clarity. Although this would create quite some churn,I think the name would be less confusing and more disassociated with the current name.
I was going to say that this change could be a bit confusing, because we've been calling `SetDefaultResource()` deprecated/discouraging it in reviews for so long. Renaming SGTM although I agree it will create quite a lot of churn.
I was going to say that this change could be a bit confusing, because we've been calling SetDefaultResource() deprecated/discouraging it in reviews for so long.
What is the alternative though? We could try to completely eliminate it and replace all usages in the other direciton (Replace `SetDefaultResource()` -> `AddResourcePath("", ...)`). My initial thinking was that this might be a harder API to get right than still providing a dedicated method to do this.
I removed all the files that are not owned by ui/webui/PLATFORM_OWNERS from this CL, and will address in follow-ups, to make it easier to land as it would require too many reviewers. Planning to actually send CLs to update the ownership to make it easier for the WebUI team to perform these horizontal changes.
PTAL as the +1 was invalidated.
source->SetDefaultResource(default_resource);Demetrios PapadopoulosRemove duplicate call?
Done
// We intentionally do not use `SetDefaultResource` here as we do not want to
// serve index.html for non-HTML paths.Comment needs to be updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Rebekah PotterPTAL. WDYT?
I am also wondering if we should rename `SeDefaultResource()` to `SetRootResource()` for more clarity. Although this would create quite some churn,I think the name would be less confusing and more disassociated with the current name.
Demetrios PapadopoulosI was going to say that this change could be a bit confusing, because we've been calling `SetDefaultResource()` deprecated/discouraging it in reviews for so long. Renaming SGTM although I agree it will create quite a lot of churn.
I was going to say that this change could be a bit confusing, because we've been calling SetDefaultResource() deprecated/discouraging it in reviews for so long.
What is the alternative though? We could try to completely eliminate it and replace all usages in the other direciton (Replace `SetDefaultResource()` -> `AddResourcePath("", ...)`). My initial thinking was that this might be a harder API to get right than still providing a dedicated method to do this.
I think the renaming would be the alternative (or something we could do in addition). My comment was supporting the renaming, not saying we shouldn't land this CL.
Replacing the other direction would be less confusing (previously deprecated method -> non deprecated method), but I agree the API is more awkward that way.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Rebekah PotterPTAL. WDYT?
I am also wondering if we should rename `SeDefaultResource()` to `SetRootResource()` for more clarity. Although this would create quite some churn,I think the name would be less confusing and more disassociated with the current name.
Demetrios PapadopoulosI was going to say that this change could be a bit confusing, because we've been calling `SetDefaultResource()` deprecated/discouraging it in reviews for so long. Renaming SGTM although I agree it will create quite a lot of churn.
Rebekah PotterI was going to say that this change could be a bit confusing, because we've been calling SetDefaultResource() deprecated/discouraging it in reviews for so long.
What is the alternative though? We could try to completely eliminate it and replace all usages in the other direciton (Replace `SetDefaultResource()` -> `AddResourcePath("", ...)`). My initial thinking was that this might be a harder API to get right than still providing a dedicated method to do this.
I think the renaming would be the alternative (or something we could do in addition). My comment was supporting the renaming, not saying we shouldn't land this CL.
Replacing the other direction would be less confusing (previously deprecated method -> non deprecated method), but I agree the API is more awkward that way.
SG. I'll follow-up with the ranaming and using it as an opportunity to update the OWNERShip of any files that are not already owned by ui/webui/PLATFORM_OWNERRS.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
WebUI: Leverage the new WebUIDataSourceImpl#SetDefaultResource().
SetDefaultResource() semantics were recently changed and it can now be
deployed in all places that were previously intentionally bypassing it,
meaning places that were calling `source->AddResourcePath("", ...)`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |