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 NonEditableFolder plugin #4899

Closed
jvigliotta opened this issue Feb 25, 2022 · 6 comments · Fixed by #4898
Closed

Remove NonEditableFolder plugin #4899

jvigliotta opened this issue Feb 25, 2022 · 6 comments · Fixed by #4898
Labels
bug:retest Retest without a specific milestone type:enhancement

Comments

@jvigliotta
Copy link
Contributor

jvigliotta commented Feb 25, 2022

Is your feature request related to a problem? Please describe.
Related to persistence vs creatability updates.

Describe the solution you'd like
Have persistence be determined by object providers.

Describe alternatives you've considered
This was the alternative... now it's not necessary.

Additional context
Directly related to:
akhenry/openmct-yamcs#113
#4323
#3741

Testing notes in: akhenry/openmct-yamcs#113

@unlikelyzero
Copy link
Collaborator

Testing Notes
on previous noneditable folder types, "VIPER" (and child folders) and "VIPER Plans", check you cannot edit or modify
you SHOULD be able to still link these items

@unlikelyzero unlikelyzero removed the needs:test instructions Missing testing notes label Mar 14, 2022
@unlikelyzero
Copy link
Collaborator

unlikelyzero commented Mar 14, 2022

Verified:

Clock object cannot be attached to Objects like VIPER Plans or VIPER objects

@unlikelyzero
Copy link
Collaborator

Re-opening because it's not possible to link a VIPER Plan to a Shared Items object view

@davetsay
Copy link
Contributor

davetsay commented Jun 9, 2022

filed this issue, #5320

@khalidadil
Copy link
Contributor

khalidadil commented Jun 27, 2022

I'm able create a link to the Day 1 plan to my folder in Shared Items, but I can also edit the name of the Day 1 plan. I'm not sure if I should close this or not. @jvigliotta?

@unlikelyzero
Copy link
Collaborator

Plans are a unicorn. We can close this out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:retest Retest without a specific milestone type:enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants