Details
-
Story
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
Description
Currently, freemarker fragments are available to use in master, however there are no ways for the user to be able to easily find out available objects to use such as themeDisplay, etc. The goal of this story is to solve this by providing auto-complete for:
- Variables when the developer types ${
- Taglibs when the developer types [@
- Resources when the developer types [resources:
Test Scenarios
Test Scenarios | Test Strategy | Kind of test | Is it covered by FrontEnd ? (JS-Unit) | Is it covered by BackEnd ? (unit or integration) |
---|---|---|---|---|
When type ${ in HTML section, the IntelliSense containing available variables popups and Auto-Complete works | Smoke | Manual | No | No |
When type [@ in HTML section, the IntelliSense containing available taglibs popups and Auto-Complete works | Smoke | Manual | No | No |
When type [resources: in HTML section of fragment, the IntelliSense containing available resources only from current collection popups and Auto-Complete works | Smoke | Manual | No | No |
If current collection doesn't has resources, when type [resources: in HTML section of fragment, the IntelliSense won't popup | Sanity | Manual | No | No |
When type ${, @[ and [resources: in CSS, JavaScript and JSON sections, the IntelliSense won't popup | Regression | Manual | No | No |
When type <lfr in HTML section, the IntelliSense containing available <lfr> tags popups and Auto-Complete works | Regression | Manual | No | No |
Attachments
Issue Links
- demands
-
LRDOCS-8580 Document auto-completion for available variables and taglibs in Fragment editor
-
- Closed
-
- is demanded by
-
LPS-95904 As a fragment developer, I would like to be able to reference valid Freemarker objects to use or have autosuggestions
-
- Reviewed
-
- relates
-
LPS-119244 Create a poshi test to cover LPS-108566
-
- Closed
-
- Testing discovered
-
LPS-109686 IntelliSense doesn't popup when append [@ to </div>
- Closed