Tarantoolsession lexer problem
Open
Nobody has claimed this yet.
internal
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
There is a problem with specific tarantoolsession code-blocks, for example, in this deployment log.
/__w/doc/doc/doc/tutorials/sql_tutorial.rst:50: WARNING: Could not lex literal_block as "tarantoolsession". Highlighting skipped.
/__w/doc/doc/doc/reference/reference_lua/box_tuple/field_path.rst:36: WARNING: Could not lex literal_block as "tarantoolsession". Highlighting skipped.
/__w/doc/doc/doc/release/1.8.rst:39: WARNING: Could not lex literal_block as "tarantoolsession". Highlighting skipped.
Reviewer: @ patiencedaur
Definition of done
- There are no errors associated with the tarantoolsession lexer in the log.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the deployment log and the tarantoolsession code blocks referenced in tutorials/sql_tutorial.rst, reference/reference_lua/box_tuple/field_path.rst, and release/1.8.rst. Trace the documentation build's lexer handling and identify why these blocks cannot be highlighted; done means the build log contains no tarantoolsession lexer errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100