Here you can find the general guidelines for maintaining the Changelog (or adding new entry). We follow the guidelines from Keep a Changelog with few additions.
- Changelogs are for humans, not machines.
- There should be an entry for every single version.
- The same types of changes should be grouped.
- Versions and sections should be linkable.
- The latest version comes first.
- The release date of each versions is displayed.
- Mention whether you follow Semantic Versioning.
... with MessageKit-specific additions:
- Keep an unreleased section at the top.
- Add PR number and a GitHub tag at the end of each entry.
- Each breaking change entry should have Breaking Change label at the beginning of this entry.
- Breaking Change entries should be placed at the top of the section it's in.
- Added for new features.
- Changed for changes in existing functionality.
- Deprecated for soon-to-be removed features.
- Removed for now removed features.
- Fixed for any bug fixes.
- Security in case of vulnerabilities.
- Added
removedCachedAttributes(for:MessageType)
,removeAllCachedAttributes()
, andattributesCacheMaxSize
toMessagesCollectionViewFlowLayout
to manage the caching of layout information for messages. #263 by @SD10.
-
Breaking Change The properties
leftStackView
,rightStackView
andbottomStackView
inMessageInputBar
are now of typeInputStackView
. The propertyseparatorLine
is also now of typeSeparatorLine
inMessageInputBar
. #273 by @nathantannar4. -
Layout information is now being cached by
MessagesCollectionViewFlowLayout
for eachMessageType
using themessageId
property. (This means if your layout is dynamic over theIndexPath
you need to handle cache invalidation). #263 by @SD10.
- Fixed a bug that prevented the
textAllignment
property ofInputTextView
'splaceholderLabel
from having noticable differences when changed to.center
or.right
. #262 by @nathantannar4.