💥 Remove deprecated schema fields #6934
Conversation
jedevc
force-pushed
the
remove-deprecated-schemas
branch
3 times, most recently
from
5b97378
to
a28466e
Compare
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
jedevc
force-pushed
the
remove-deprecated-schemas
branch
from
a28466e
to
7fd9249
Compare
jedevc
force-pushed
the
remove-deprecated-schemas
branch
from
7fd9249
to
8227f00
Compare
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
jedevc
force-pushed
the
remove-deprecated-schemas
branch
2 times, most recently
from
b1a2a2f
to
306331e
Compare
jedevc
force-pushed
the
remove-deprecated-schemas
branch
from
306331e
to
768c441
Compare
This fields have been deprecated for several months at this point - so we should finally remove them (in v0.11.0, which is a minor release). Use of these functions outside of SDK internals was low anyways, so we should see minimal breakages even if users were using these. Signed-off-by: Justin Chadwell <me@jedevc.com>
jedevc
changed the title
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Removes previously deprecated fields - we've had these fields deprecated for several months at this point, so hopefully this should cause minimal impact.