Skip to content
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

Bugfix/code snippet #105

Merged
merged 3 commits into from
Jan 28, 2019
Merged

Bugfix/code snippet #105

merged 3 commits into from
Jan 28, 2019

Conversation

lievenvg
Copy link
Contributor

PR Checklist

This PR fulfills the following requirements:

  • The commit message follows our guidelines: Contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A changelog entry was added

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

App is responding very slowly and is cpu intensive.

Issue Number: #62

What is the new behavior?

App is responding smoothly.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Resolved issues

Closes: #62
Fixes: #62
Resolves: #62

@@ -36,7 +36,7 @@ export class CodeSnippetComponent implements OnChanges, AfterViewChecked {
if (this.processMarkdown) { this.codeSnippet = marked(this.codeSnippet); }
}

public ngAfterViewChecked() {
public ngAfterViewInit() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this re-highlight when the codeSnippet attribute is changed?

Copy link
Contributor Author

@lievenvg lievenvg Jan 25, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in person, the previous and new behaviour don't support dynamic updating of the highlighting. I opened a separate issue #107 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Examples are really CPU intensive (while they shouldn't)
4 participants