use KPackage::fileUrl to support rcc KCMs packages
ClosedPublic

Authored by sitter on Feb 27 2019, 11:21 AM.

Details

Summary

the previous code would construct file:// URIs. instead, leave the url
construction to kpackage so we get either file:// or qrc:// depending on
the actual type of the package

Test Plan
  • cmake pass
  • make pass
  • make test pass

Diff Detail

Repository
R296 KDeclarative
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
sitter created this revision.Feb 27 2019, 11:21 AM
Restricted Application added a project: Frameworks. · View Herald TranscriptFeb 27 2019, 11:21 AM
Restricted Application added a subscriber: kde-frameworks-devel. · View Herald Transcript
sitter requested review of this revision.Feb 27 2019, 11:21 AM
apol accepted this revision.Feb 28 2019, 4:29 PM
apol added a subscriber: apol.

Makes sense, it would make sense to see if we can come up with a check for such things. I wonder if filePath should be deprecated actually as it's better dealt by the host application.

This revision is now accepted and ready to land.Feb 28 2019, 4:29 PM

LXR seems to show a whole bunch of these code segments https://lxr.kde.org/search?_filestring=&_string=package.filePath

Deprecation is probably a good idea. From where I am standing an application can always grab the path out of an url if absolutely necessary.

This revision was automatically updated to reflect the committed changes.