Cicero UI Components v0.3.9

💅 Polish

• #255: Remove ErrorLogger entirely when no errors exist (@irmerk)

Cicero UI Components v0.3.8

💅 Polish

• #254: Correct font size for Navigation header (@irmerk)

Cicero UI Components v0.3.7

🏃‍♀ Performance

• #252: Allow full functionality of paste to new clause templates (@irmerk)

Cicero UI v0.3.6

🐛 Bug Fix

• #250 : Removes styling that overrides semantic-ui to prevent interference when parent app is also using semantic-ui

Cicero UI v0.3.5

🐛 Bug Fix

#249: Update search cursor in Template Library to be same color as search text (@DianaLease)

Cicero UI v0.3.4

🚀 This release includes several dependency upgrades, bug fixes and brand new support for cut/paste in the ContractEditor component.

🚀 Features

• New Cut/Paste support in the contract editor
• Search improvements: New styling for search box, ability to search on display name, allow color customisation

🐛 Bug fixes

• Addresses issues with empty paragraphs between clauses
• Addresses a library bug when a template does not have a display name
• Protect error component against bad input

🏠 Internal

• New API call to check if a clause is supported by the editor
• New onUndo handler
• Upgrade to Markdown Transform 0.9.2
• Upgrade to Markdown Editor 0.8.3
• Upgrade to Cicero 0.20.5

Cicero UI Components v0.3.3

🚀 New Feature

• #231 : Users can now pass optional VARIABLE_COLOR and/or COMPUTED_COLOR attributes with their clauseProps to customize the color of rendered variables.

Cicero UI Components v0.3.2

🏠 Internal

#229 : Increment support for markdown-editor (@DianaLease )

Cicero UI Components v0.3.1

🚀 New Feature

• #134 : Copy + Paste now duplicates a clause and its template, then parses (@DianaLease @irmerk)

Cicero UI Components v0.3.0

💥 Breaking Change

• #223 : Refactors parseClause to be onClauseEdited, which takes a clause node as its single argument (@DianaLease )

🚀 New Feature

• #223 : Adds computedPlugin to handle computed expressions in cicero 0.20 (@DianaLease )

🐛 Bug Fix

• #223 : Fixes a bug when checking if a user's selection is inside a variable. Now, if a user selects multiple nodes and is not solely within one variable, they will not be able to edit it. (@DianaLease )