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

[Custom Fields/Plugins] Move custom field types to extensions so plugins can add new types #488

Closed
jstanden opened this Issue Oct 26, 2017 · 1 comment

Comments

Projects
1 participant
@jstanden
Copy link
Owner

jstanden commented Oct 26, 2017

No description provided.

@jstanden jstanden added this to the 8.3 milestone Oct 26, 2017

@jstanden jstanden added this to TODO in Planning Dec 19, 2017

@jstanden jstanden moved this from TODO to In Development in Planning Dec 19, 2017

@jstanden jstanden modified the milestones: 8.3, 8.4 Mar 4, 2018

@jstanden jstanden modified the milestones: 8.4, 9.0 Jun 9, 2018

@jstanden jstanden moved this from In Development to TODO in Planning Jul 13, 2018

@jstanden jstanden added this to the 9.1 milestone Nov 2, 2018

@jstanden jstanden added this to To do in 9.2 via automation Nov 2, 2018

@jstanden jstanden removed this from TODO in Planning Nov 2, 2018

@jstanden

This comment has been minimized.

Copy link
Owner

jstanden commented Nov 2, 2018

Implemented in 9.1!

@jstanden jstanden closed this Nov 2, 2018

9.2 automation moved this from To do to Completed Nov 2, 2018

jstanden added a commit that referenced this issue Dec 18, 2018

* [Developers/Custom Fields] New custom field types can be implemente…
…d in plugins using the `cerb.custom_field` extension point.

Fixes #488
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment