D4672: Initial support for hookup of projects with general (web) services
Friedrich W. H. Kossebau
noreply at phabricator.kde.org
Thu Nov 16 13:36:39 UTC 2017
kossebau added a comment.
In https://phabricator.kde.org/D4672#168433, @apol wrote:
> Maybe instead of having all of the configuration UI's a better first approach would be to detect the plugins we can use from what's in the repository?
> For example github we can detect by checking .git/config or, well, `git remote show origin`. With phabricator we can look for the `.arcconfig` file.
Yes, reading existing data should be done when possible, good hint. I had not yet invested in such data finding code, so far concentrated on the service/plugin APIs to develop some sane structures.
A use-case I have in mind though is also supporting multiple instances of services. I have worked in setups with a private and public instance of same service, for keeping private/customer data separate from public/community data. So the data about services in the repo was not complete, and one would still need a UI to enter service data.
But pre-filling with detected existing data is a good idea, agreed.
To: kossebau, #kdevelop, mwolff
Cc: apol, ngraham, mwolff, kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel