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

Remove apps that will go to market from shipped.json #27985

Merged
merged 2 commits into from
May 24, 2017
Merged

Conversation

PVince81
Copy link
Contributor

@PVince81 PVince81 commented May 23, 2017

Description

Makes it possible to uninstall them.

Related Issue

#27983

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

I don't have full understanding of the extent of the "shipped" flag. Grepping for isShipped seems to show a lot of locations, even some related to API responses.

@tomneedham @DeepDiver1975 @davitol

Makes it possible to uninstall them.
@PVince81 PVince81 added this to the 10.0.2 milestone May 23, 2017
@davitol
Copy link
Contributor

davitol commented May 23, 2017

Tested and WFM 👍

@PVince81
Copy link
Contributor Author

Thanks. Don't merge yet, there could be consequences due to the weird OCS code that rely on this flag.

Needs to be evaluated

@tomneedham
Copy link
Contributor

tomneedham commented May 23, 2017

So grepping all of these apps to show what OCS routes they might register:

./activity/appinfo/routes.php://API::register(
./activity/appinfo/routes.php://API::register(
./activity/appinfo/routes.php:API::register(
 ./notifications/appinfo/routes.php:\OCP\API::register(
./notifications/appinfo/routes.php:\OCP\API::register(
./notifications/appinfo/routes.php:\OCP\API::register(
./notifications/tests/Integration/app/appinfo/routes.php:\OCP\API::register(
./notifications/tests/Integration/app/appinfo/routes.php:\OCP\API::register(
./sharepoint/appinfo/routes.php:OC_API::register('get', '/apps/sharepoint/api/v1/mounts',

@tomneedham
Copy link
Contributor

My only concern at the moment is if apps are enhancing the notification or activity apis - looking for usages...

@PVince81
Copy link
Contributor Author

AFAIK none of our apps are expecting more than a single response block.

Does it make a difference is shipped is there or not ? Does it influence the order or name of the response block ?

"files_videoplayer",
"firewall",
"firstrunwizard",
"gallery",
"market",
Copy link
Member

Choose a reason for hiding this comment

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

Kill market as well

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this will allow uninstallling the market app, (P)roceed, (A)bort ?

Copy link
Member

Choose a reason for hiding this comment

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

If somebody wants to....

@PVince81
Copy link
Contributor Author

My only concern at the moment is if apps are enhancing the notification or activity apis - looking for usages...

Enhancing ? How ?

@PVince81
Copy link
Contributor Author

and why

@tomneedham
Copy link
Contributor

Enhancing ? How ?

well by latching onto the same route and altering / changing the response in some weird way

and why

no idea

@PVince81
Copy link
Contributor Author

removed "market".

@tomneedham is checking whether it's really possible to extend/overwrite the endpoints in 10.0. Because from what I remember we removed this possibility a long time ago when unifying the APIs. (something about integrating with app framework I think)

@tomneedham
Copy link
Contributor

Just checked with 10.0.1 => You can still 'extend' existing routes by registering for the same route and returning data - the responses are then 'merged'. This is done using array_merge with priority given to shipped apps. Collisions would only occur when using the same keys in the responses.

@PVince81
Copy link
Contributor Author

@tomneedham thanks. This kind of weird overriding of routes isn't officially supported. I thought we properly removed this already. Might need more work for this.

This means at this point we will remove the apps anyway from shipped.json. The likeliness of someone overwriting routes like this is anyway minimal.

Waiting for CI then merge

@PVince81
Copy link
Contributor Author

@davitol did you test the checkboxes I posted above ? If yes, please tick

@PVince81
Copy link
Contributor Author

@lock
Copy link

lock bot commented Aug 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants