-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Do not return x_by
fields for v2 API
#10286
Labels
Comments
kirrg001
added
server / core
Issues relating to the server or core of Ghost
affects:api
Affects the Ghost API
labels
Dec 14, 2018
kirrg001
added a commit
to kirrg001/Ghost
that referenced
this issue
Dec 17, 2018
refs TryGhost#10286 - we want to deprecate all `x_by` fields - we would like to get rid of all usages to be able to easily remove the fields in the future - `invitedBy` is not used in the admin client
This was referenced Dec 17, 2018
kevinansfield
pushed a commit
to TryGhost/Admin
that referenced
this issue
Dec 17, 2018
refs TryGhost/Ghost#10286 - not used - looking for more information? visit TryGhost/Ghost#10291
kirrg001
added a commit
that referenced
this issue
Dec 17, 2018
kirrg001
added a commit
to kirrg001/Ghost
that referenced
this issue
Jan 3, 2019
refs TryGhost#10286 - v2 no longer exposes x_by fields (published_by, updated_by, created_by) - we will add a brand new concept called activity stream/actions soon
kirrg001
added a commit
that referenced
this issue
Jan 3, 2019
refs #10286 - v2 no longer exposes x_by fields (published_by, updated_by, created_by) - we will add a brand new concept called activity stream/actions soon
kirrg001
added a commit
to kirrg001/Ghost
that referenced
this issue
Jan 21, 2019
refs TryGhost#10286 - this is just a hotfix for v0.1 - we keep the x_by fields for now and deprecate them - as soon as an integration updates/inserts a resource, we just store the owner ID - we currently work on a new concept for v2 - v2 no longer exposes or uses x_by, see TryGhost#10294
kirrg001
added a commit
that referenced
this issue
Jan 21, 2019
) refs #10286 - this is just a hotfix for v0.1 - we keep the x_by fields for now and deprecate them - as soon as an integration updates/inserts a resource, we just store the owner ID - we currently work on a new concept for v2 - v2 no longer exposes or uses x_by, see #10294 - we need to iterate on this change, because we currently use the naming `context.api_key_id` in the auth/API layer
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What
We decided to burn the
x_by
fields in API v2.Instead, we will introduce a new concept/feature for v2, coming soon. I will link the issue here as soon as it's fully written down.
Why
V2 is still in active development.
x_by
columns #10295)x_by
fields in codebaseThe text was updated successfully, but these errors were encountered: