Record lost component fields in comment: Status History

Below is the history of changes to this idea's status. Return to the idea.

  • Not Considering

    Agree with the previous review status

    "Schema changes are considered high impact changes in general. Why would you remove a Schema field if you expect that you want to add it back in the future?

    Do you want to temporarily hide the field from authors/editors in the GUI? In that case, would it be an option to keep the field in the underlying data?"

    Hiding a field might be interesting although it requires a use case

    Due to inactivity in discussions and votes, we are not considering this idea

    Andriy Zhidko

  • Under Community Review

    We would like to understand your use case better.  

    Schema changes are considered high impact changes in general. Why would you remove a Schema field if you expect that you want to add it back in the future?

    Do you want to temporarily hide the field from authors/editors in the GUI? In that case, would it be an option to keep the field in the underlying data?

    Rick Pannekoek

  • New

    No note was provided with this status update.

    Neil Gibbons