Release Notes: October 2017 Release

Repositories

This release consists of the following new versions of the livingdocs-server, the livingdocs-editor and the livingdocs-framework:

Livingdocs Server

How to require the server in your package.json:

"dependencies": {
  "@livingdocs/server": "63.2.1",
}

• Link to the release branch: https://github.com/livingdocsIO/livingdocs-server/tree/release-2017-10
• Previous release: 61.2.1

Livingdocs Editor

How to require the editor in your package.json:

"dependencies": {
  "@livingdocs/editor": "23.0.3",
}

• Link to the release branch: https://github.com/livingdocsIO/livingdocs-editor/tree/release-2017-10
• Previous release: 20.10.4

Livingdocs Framework

The framework is already integrated in the package.json of the upstream server and editor. It’s not necessary to integrate the framework from your side.

The framework does not have a release branch.

How to require the framework in your package.json:

dependencies: {
  "@livingdocs/framework": "7.14.0"
}

• Previous release: 7.12.2

Component changes

Known issues

In detail

Upgrade to node 8

• We upgraded to node 8, most likely it will not have a big impact on you if you already use Docker. We can use newer features from now on. There are big changes in low level components like an improved debugger, async/await, n-api, async_hooks and v8. You can read more about it here: https://nodejs.org/en/blog/release/v8.0.0/

• There was one bigger issue we ran into. The behavior of the Date constructor changed in this node version. new Date(isoString) is now timezone agnostic. That behavior changed in ES2015 and node/chrome now respect that.

With node 6:

new Date('2015-05-04T00:00:00')  // 2015-05-04T00:00:00.000Z
new Date('2015-05-04T00:00:00Z') // 2015-05-04T00:00:00.000Z

With node 8:

new Date('2015-05-04T00:00:00')  // 2015-05-03T22:00:00.000Z
new Date('2015-05-04T00:00:00Z') // 2015-05-04T00:00:00.000Z

• We use and advise you to use npm version > 5.5. npm publish had an issue where the test directory at the root of a project didn’t get published in the final package tar file on npm. https://github.com/npm/npm/issues/18341. npm v5.1 version which gets shipped with node 8.9 fixes that issue.

• When you switch to node 8 please also install all local modules from scratch (or npm rebuild):

  nvm install 8 && nvm alias default 8
  rm -Rf ./node_modules && npm install
  

• npm 5 which gets shipped with node 8 has a few issues with npm link. If you depend on them, you might want to downgrade to an older npm version using npm install -g npm@3.

Remove deprecated methods

• DocumentVersion.prototype.render got removed. Please call renderPipeline.renderDocumentVersion({documentVersion}, cb) directly.
• Removes transform methods from generic_document model. Downstreams might depend on this model in tests.
• Removes exported renderDocument and renderDocumentVersion on the render-pipeline file. Please use the renderPipeline instance using

liServer.features.api('li-render-pipeline').renderDocumentVersion

• Removes renderPipeline.renderDocument. Please use the renderPipeline.renderDocumentVersion({documentVersion}, cb) method instead.
• From now on we don’t export the designLoader methods on the design feature file anymore. Please use the designLoader feature instead:

liServer.features.api('li-design-loader').load({name, version}, cb)

• Removes exports from cache api. Please use liServer.features.api('li-cache') instead.
• Removes searchApi.getSearchManager and searchApi.getEsClient. Please use liServer.features.api('li-search').searchManager if you really need it.
• Removes require('@livingdocs/server/app/features/documents').publicationApi. If you still depend on deep requires, please replace them with the proper api. e.g. `liServer.features.api(’li-documents’).publication.
• Removes ``DocumentEntitiesManager.getDocumentAndRevision. Please use DocumentEntitiesManager.getVersion` instead.

Content fixes for drag’n’drop huGO articles

• HugoArticle class was parsing only paragraphs (<p>-tags). We are now parsing subtitles as well (<h2>-tags).

New body property in HugoArticle

Instances of the HugoArticle class now additonally have a body property which holds an array of objects describing the content. Given the following huGO article body:

<p>Paragraph One.</p>
<h2>Subtitle One.</p>
<p>Paragraph Two.</p>

after parsing the body property would contain:

[
  {
    content: 'Paragraph One.'
    type: 'paragraph'
  },
  {
    content: 'Subtitle One.'
    type: 'heading2'
  },
  {
    content: 'Paragraph Two.'
    type: 'paragraph'
  }
]

whereas the text property - which is kept - contains:

[
  'Paragraph One.',
  'Paragraph Two.'
]

The <h2/>-headings have been omitted in the latter case.

Configuration

Which tags are allowed to be parsed can be configured:

hugo: {
    // [...]
    parsedBodyTags: {
      h1: 'heading1',
      h2: 'heading2',
      p: 'paragraph'
    }
  },

In case the tags are not configured the default is:

{
  h2: 'heading2',
  p: 'paragraph'
}

Fix render pipeline api error handling

An asynchronous function of a render_pipeline_api should call the callback with an error, not throw errors directly. Otherwise the users of the api cannot handle the error nor log additional informations to find the document which caused the problem.

Makes migrations 086-087 work again for older releases

Removes the deprecated group_projection and group_member_projection tables. They got replaced in migration #085 about 8 months ago. If you’re using the regular apis, this doesn’t have an impact on your code.

Remove newrelic support

This removes the instrumentation library from the project. We’ve never used it and will most likely replace it with sth like opentracing.

Remove disableHugoUpdates check in favor of hugo updateConditions

import now accepts an optional updateCondition parameter. This parameter can be a string referring to one of three common update strategies configured downstream and implemented upstream: never, always, untouched - or alternatively a function implementing custom logic can be passed.

// app/features/import/import_api

import ({importJob, rawDocument, shouldCreateNew, updateCondition, userId}, callback) {
  // ...
}

Limit dropdown items through configuration

For dropdowns we’re using ui-select. ui-select has issues handling big data. We implement the limitTo provided by ui-select to limit the amount of data displayed at once to a configurable value. If the configuration is missing or undefined this parameter will not apply.

Example for config:

name: 'royaltyRecipientIds'
  form: 'li-meta-multiselect-form'
  config:
    service: 'nzzRoyaltyRecipients'
    halfWidth: false
    label: 'Royalty Recipient'
    placeholder: 'Select a royalty recipient...'
    limitTo: 500

Image caption isn’t imported from Hugo

After d’n’d-ing an image the response data looks like the following:

{
    "url": "http://nzz-img-dev.s3.amazonaws.com/2017/10/25/d5ca8539-caa5-4cbf-ac82-4cb6de79a565.jpeg",
    "width": 4800,
    "height": 3200,
    "size": 13422989,
    "mime": "image/jpeg",
    "hugoPicture": {
        "id": "picture-1917895495",
        "url": "https://hugo-fpro-prd.nzz.ch/file_provider/?group=BILD&entry=04FBC820_09EBFA0B670B&validTo=1509036448&consumer=hugoAPI&signature=850a5730697ca61d7cfddbc1460ec92c8f142568&mts=21102017160930",
        "height": "3200",
        "width": "4800",
        "author": "ALEXANDRA WEY",
        "credit": "KEYSTONE",
        "agency": "NZZ – Agentur Keystone",
        "source": "KEYSTONE",
        "copyright": "© KEYSTONE /  ALEXANDRA WEY",
        "caption": "ARCHIVBILD ZUM RUECKTRITT VON TENNISSPIELER MARCO CHIUDINELLI --- Marco Chiudinelli of Switzerland celebrates after defeating Yaraslav Shyla of Belarus during the fifth match of the Davis Cup world group playoffs between Switzerland and Belarus, Switzerland, Sunday, September 17, 2017. (KEYSTONE/Alexandra Wey)",
        "note": "",
        "hugoTimestamp": "2017-10-21T16:09:30",
        "contentCreatedAt": "2017-09-17T00:00:00"
    }
}

• There’s no more hugoData object and the caption is inside hugoPicture.
• The test design’s image component now accommodates a caption.

Extend field extractor for doc-style

Extends the field extractor to also be able to extract style directives.

The configuration of a style extraction looks like this:

	identifier: 'textColor'
	type: 'style'
	style: 'color'
	matches: ['multiple-styled-component.background']

This will look in the component multiple-styled-component on the directive background and extract the style color.

A serizalized component like this:

'multiple-styled-component': {
  text: 'I am styled'
  background: {'css-background-color': '#000', 'color': '#fff'}
}

would lead to the field textColor to be extracted to #fff.

The resulting markup has the full content object with all styles in content and the selected style in style. If no style is set, only the content is returned.

Remove Option to Configure the Publish Panel Metadata Forms in the Editor

• Removed the option to configure the publish panel metadata forms in the editor (metadata in config/environments/all.coffee is now ignored).
• Move the metadata form configuration to the server like described here: https://github.com/livingdocsIO/livingdocs/blob/master/concepts/metadata/metadata-examples.md#server.

Introduce card-based design on the publishing screen

Patches

Editor

• 23.0.3 - addTask method invocation

Server