-
Notifications
You must be signed in to change notification settings - Fork 467
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
Edit Contentlet: Implement feature flag #26163
Comments
#26242) * dev (general): add new library and route * dev (configuration resource Java): Add Feature Flags to WhiteList * copywritting (edit-content routing): change name to match standard * dev (edit content guard): add guard to prevent navigation without feature flag * dev (app routing): add guard to edit content and move pages route to angular * fix (general): add guard to providers and fix bad use of inject * dev (custom event handler): add feature flag to redirect to new form instead of jsp old dialog * fix (general test): test were broken by bad import in providers * fix (form component test): missing import * dev (general): add routing for creating contentlet * dev (dot custom event handler): add re routing for edit task * dev (dot pages store): add redirect to new portlet when feature flag is on * fix (pages portlet): some tests were broken * dev (dot edit page nav): Add redirect to new edit contentlet * fix (pages create dialog): route were wrong * Revert "dev (dot edit page nav): Add redirect to new edit contentlet" This reverts commit d9a3f9f. * dev (jsp): add contentType to event * dev (dot custom event handler service): add event for create contentlet from edit page * dev (general): final replace of the route to content * dev (general): solve feedback * feedback (edit content guard): change the approach to be functional guard * feedback (general): add tests and small refactor * feedback (general): small refactor * feedback (feature flags): fix content editor 2 value * dev (dot properties service): add methods to get feature flags values directly * dev (jsp): edit redirects now sends the content type in the event * dev (host jsp): now host emits a different event to go to legacy portlet * dev (custom event handler): refactor to handle new feature flag method and verify content types * fix (custom event handler): tests were broken * fix (dot properties service): Add missing done callback * dev (general): apply refactor for new feature flag method * fix (dot feature flag resolver): test were broken * dev (dot pages): add redirect to new edit contentlet checking the content types * fix (pages store): fix tests * feedback (general): change name of methods * feedback (general): fix feature flag name
Note to QA:With the flags disabled, you need to make sure that the edit content is working as usual in the following sections:
This includes create, edit, archive, delete, workflow actions and any other operation related to contentlets and pags (folder not included). For sites, events, and vanity url we will be doing another issue. Now if the feature flag is on, then you will see a new blank page with a hello world and a new url based on |
|
Working on it! |
Note: Fixed by re-deploying again. @zJaaal |
Nice! |
Approved: Tested on master_74c2a31_SNAPSHOT, Docker, macOS 13.0, FF v113.0 |
#26242) * dev (general): add new library and route * dev (configuration resource Java): Add Feature Flags to WhiteList * copywritting (edit-content routing): change name to match standard * dev (edit content guard): add guard to prevent navigation without feature flag * dev (app routing): add guard to edit content and move pages route to angular * fix (general): add guard to providers and fix bad use of inject * dev (custom event handler): add feature flag to redirect to new form instead of jsp old dialog * fix (general test): test were broken by bad import in providers * fix (form component test): missing import * dev (general): add routing for creating contentlet * dev (dot custom event handler): add re routing for edit task * dev (dot pages store): add redirect to new portlet when feature flag is on * fix (pages portlet): some tests were broken * dev (dot edit page nav): Add redirect to new edit contentlet * fix (pages create dialog): route were wrong * Revert "dev (dot edit page nav): Add redirect to new edit contentlet" This reverts commit d9a3f9f. * dev (jsp): add contentType to event * dev (dot custom event handler service): add event for create contentlet from edit page * dev (general): final replace of the route to content * dev (general): solve feedback * feedback (edit content guard): change the approach to be functional guard * feedback (general): add tests and small refactor * feedback (general): small refactor * feedback (feature flags): fix content editor 2 value * dev (dot properties service): add methods to get feature flags values directly * dev (jsp): edit redirects now sends the content type in the event * dev (host jsp): now host emits a different event to go to legacy portlet * dev (custom event handler): refactor to handle new feature flag method and verify content types * fix (custom event handler): tests were broken * fix (dot properties service): Add missing done callback * dev (general): apply refactor for new feature flag method * fix (dot feature flag resolver): test were broken * dev (dot pages): add redirect to new edit contentlet checking the content types * fix (pages store): fix tests * feedback (general): change name of methods * feedback (general): fix feature flag name
Parent
#25445
User Story
As a stakeholder, I want you to implement the feature flags for the new edit contentlet screen.
Acceptance Criteria
DOT_CONTENT.EDITOR2.ENABLE=true
andDOT_CONTENT.EDITOR2.CONTENT_TYPE=*
herelibs/edit-content
and make the structure like this:core-web/apps/dotcms-ui/src/app/api/services/dot-custom-event-handler/dot-custom-event-handler.service.ts
and the sections where it should load are:Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
create-contentlet
,edit-page
andedit-contentlet
I think are the one we are going to need.Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
Sub-Tasks & Estimates:
The text was updated successfully, but these errors were encountered: