[MGNLFE-18] Rename libs from @magnolia/react-renderer to @magnolia/react-editor Created: 22/Jan/20  Updated: 27/Apr/20  Resolved: 03/Mar/20

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.0

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLFE-29 Rename 'RenderContext' to 'EditorCont... Closed
dependency
is depended upon by MGNLFE-19 Publish frontend libs to npm Closed
is depended upon by MGNLFE-24 DOC: Components and libraries renamed Closed
relation
is related to MGNLFE-13 Rename SPA components Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: SPA Editor
Sprint: 6.2 Ramp-up 17, 6.2 Ramp-up 18
Story Points: 1

 Description   

Rename libs from:

@magnolia/react-renderer to @magnolia/react-editor

@magnolia/angular-renderer to @magnolia/angular-editor

Reason is that while "renderer" kind of makes sense to Magnolians - who see it as an alternative to rendering with freemarker, it won't make sense to frontend developers.

React and Angular are already renderers by their very nature - or they will think it is about SSG static site generation - or SRE - server side rendering of the an SPA.

The library name should describe the value that it adds - "editor" gets to the heart of it and a front end developer will be intersted in something that "edits" a React app.

Its also consistent with the component renaming proposed in MGNLFE-13


Generated at Mon Feb 12 05:43:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.