Follow up for #111715-53: Convert node/content types into configuration (See #54 too.)

Problem/Motivation

node type table is not used anymore.

Proposed resolution

hook_node_info() can be removed.

Remaining tasks

This needs filled out. (reviews needed, tests to be written or run, documentation to be written, etc.)

User interface changes

No UI changes.

API changes

Yes. removing hook_node_info()

Comments

YesCT’s picture

YesCT CreditAttribution: YesCT commented
Issue tags: +challenging

This might be a self contained task that someone could jump into.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Title: remove hook_node_info after Convert node/content types into configuration » Remove Node Type API for in-code node types after Convert node/content types into configuration
Component: node.module » node system
Priority: Minor » Major

This issue should eliminate the entire "node system" component that we currently have, and which I'm assigning this issue to.

Essentially, by getting rid of hook_node_info(), we actually remove the entire Node Type API.

That API is used by old and legacy modules in core only; i.e., Poll, Book, (more?)

With content types converted to configiguration entities, it doesn't make sense anymore and has lost its entire meaning. :)

andypost’s picture

andypost
he/him
Primary language Russian
CreditAttribution: andypost commented

Some of this already addressed in #111715: Convert node/content types into configuration

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented
Status: Postponed » Closed (duplicate)

There is AFAIK nothing left to do here after #111715: Convert node/content types into configuration in it's current state. The hook is gone and node_type callbacks are all gone.