You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we are implementing wpgraphql with acf at the moment. I'm very happy with the experience so far. My question is more about workflows and maybe there is already a technical solution to it. We are working in a team on different features at the same time. So every time we have to retire a field we have to support it for as long as old querys are still present on those branches. What is your best practice to handle it? At least we want to hide those fields from our cms editors. Is there a way to set them as deprecated so that a technical solution is attainable?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
we are implementing wpgraphql with acf at the moment. I'm very happy with the experience so far. My question is more about workflows and maybe there is already a technical solution to it. We are working in a team on different features at the same time. So every time we have to retire a field we have to support it for as long as old querys are still present on those branches. What is your best practice to handle it? At least we want to hide those fields from our cms editors. Is there a way to set them as deprecated so that a technical solution is attainable?
Beta Was this translation helpful? Give feedback.
All reactions