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

[Fatih, Emin] Domain-specific Features #328

Closed
2 tasks done
FatihAkgoz opened this issue Dec 3, 2024 · 3 comments
Closed
2 tasks done

[Fatih, Emin] Domain-specific Features #328

FatihAkgoz opened this issue Dec 3, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request front end related to the app's graphical design, request and response management priority: high web

Comments

@FatihAkgoz
Copy link
Contributor

FatihAkgoz commented Dec 3, 2024

          Domain-specific features (e.g. why they're specific, how they're implemented):
  • Improvements on syntax highlighting in code execution blocks: In the code execution blocks that users can add in their questions, syntax highlighting is implemented in order to improve readability of the code. It also improves user experience since it provides a familiar environment that programmers usually make developments. The implementation of syntax highlighting was initialized, not finalized, but it should be improved based on the feedback we got from customer. There is syntax highlighting as it is on milestone 2, but not all the keywords or conventionally highlighted elements are highlighted. Also it should be more engaging visually in terms of colors etc. Also if it's possible -it's in the scope of the syntax highlighter API we use- language-specific highlighting should be implemented. If the API we were using to implement syntax highlighting permits to make those changes, these should be implemented as well.

  • Acceptance Criteria: There should be language-specific syntax highlighting with more engaging color palette.

  • Example Usage:
    syntax-highlighting

  • Improvements on code execution output display: The output of the code snippet that has run by user should be visible right below the aforementioned snippet. Since we are working on a programming language forum, the conventional code running mechanisms and designs should be implemented to gain acceptance by the community. This would improve user experience significantly and needed to be improved based on the feedback we got from customers. In milestone 2, there were bugs that causes to outputs to displayed at the end of the question details page. It should be displayed in a more visually logical place.

  • Acceptance Criteria: The output of the code snippet should be displayed at the right under the related code snippet, under the "Run Code" button.

  • Example Usage: Code Execution Web Mockup

Originally posted by @ceylingebes in #326 (comment)

@FatihAkgoz FatihAkgoz added enhancement New feature or request priority: high front end related to the app's graphical design, request and response management web labels Dec 3, 2024
@FatihAkgoz FatihAkgoz changed the title Domain-specific features (e.g. why they're specific, how they're implemented): Domain-specific Features Dec 3, 2024
@FatihAkgoz FatihAkgoz added this to the 451 - Final Milestone milestone Dec 3, 2024
@FatihAkgoz FatihAkgoz changed the title Domain-specific Features [Fatih, Emin] Domain-specific Features Dec 3, 2024
@FatihAkgoz
Copy link
Contributor Author

Code execution outputs were seperated for questions, comments and try your own code sections.

@FatihAkgoz
Copy link
Contributor Author

Since syntax highlighing caused issues integrating annotations we have decided to prefer annotation for code blocks.

@mehmeteminipekdal
Copy link
Contributor

Syntax highlighting issues are resolved and highlighting is added to frontend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request front end related to the app's graphical design, request and response management priority: high web
Projects
None yet
Development

No branches or pull requests

2 participants