This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
T/53a: Split "heading" command into independent commands. #58
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e76a030
Split the HeadingCommand.
oleq 811e3d7
Integration with ParagraphCommand. Use getSelectedBlocks() in
oleq 611dcf3
Removed obsolote code from HeadingCommand tests. Docs refactoring.
oleq cb71790
HeadingCommand passes selection to the ParagraphCommand instead of el…
oleq 7b2c1c8
Removed HeadingEngine#commands. Simplified config.heading.options loc…
oleq 65ac56c
Code refac. Deobfuscated some pieces of code. Allowed custom title fo…
oleq File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it have to be a model instance? Can't this be a simple object?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Binding requires observable. We could pass an object here and convert it into observable in createlistdropdown. But this is beyond the scope of this issue as it didn't change this part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OTOH I'm not sure whether would make more sense. There could be cases when a feature using the dropdown might want to play with models in
#items
immediately, i.e. bind its attributes to something else.If we enforce that
#items
isCollection.<Object>
, developers would need to pick those models from the dropdown aftercreateListDropdown
was called which is not very convenient.Besides, what would
ListView
look like then if#items
would beCollection.<Object>
? Where to store the "intermediate models" created increateListDropdown()
? Because there must be models forModel->ListItemView
bindings.