Giter Site home page Giter Site logo

infovizion-code's Introduction

InfoVizion tools

Set of developement tools used in InfoVizion for Qlik projects

Qlik Load Script support

F5: run default command, can be check and reload, just reload, or just check script

Control Shift L: opens windows on corresponding log file for last execution.

//#!QV_SUPPRESS_ERROR comment suppress parsing errors for one QVS statement //#!QV_SKIP_PARSING comment suppress parsing errors for all remaining lines in file

QVD Support:

Just click on QVD in left panel to see QVD metadata in preview window

Expression file support

Extension works for files with extension qlikview-vars.

For each save corresponding json file should be created. Only most severe errors would be checked on that stage: Some examples:

  • -- instead of --- tag as delimiter between expressions
  • Circular references in formulas (in dollar sign expansion)

F5 run more detailed check, including check for undefinded variables, circular references, Qlik Expression syntax check and so on.

To introduce undefined variables one can use pseudo excression LoadScriptVariables To suppress parse errors for one expression one can add tag pragma with value skipError

See example:

---
set: LoadScriptVariables
definition: vU.CurrentDate=15234,vU.StartDate='01.03.2012', vG.MaxValue=20
description: Перечисление переменных, устанавливаемых в скриптах загрузки. Со значениями которые будут подствавляться во время проверки правильности 
   формул, которые эти переменные используют. Формат: ИмяПеременной1=14234,ИмяПеременной2='ПримерСтроковогоЗначения'
---
set: СуммаПродажи
definition: (-Sum({<ТипДокумента={'Sales'},_Current={1},_ФлагДействующаяДата={1}>} Сумма)) ( ABRAKADABRA )
pragma: skipError
label:Продажи, руб
---
set: СуммаПродажиДоляНакопительно
definition: RangeSum(-Sum({<ТипДокумента={'Sales'},_Current={1},_ФлагДействующаяДата={1}>} Сумма)
                    /-Sum({<ТипДокумента={'Sales'},_Current={1},_ФлагДействующаяДата={1}>} TOTAL Сумма),0,RowNo())
label:% накопительно по продажам

Standard Ctrl + / combination comment / uncomment block with # style comments

infovizion-code's People

Contributors

vadimtsushko avatar

Watchers

 avatar  avatar

infovizion-code's Issues

Support Workspace Trust

Hello 👋 I'm from the VS Code team.

Recently, we have been exploring a security feature we refer to as Workspace Trust. This feature is intended to centralize and unify a security conscious decision required by a variety of VS Code features. With workspace trust, the user will be able to declare whether or not they trust the folder that is opened in VS Code before these features are executed.

Why you should care

We want to make sure that those users have a delightful experience with workspace trust and that includes extension authors deciding how much of their extension is supported in an untrusted workspace.

Workspace Trust experience

You can enable the feature with the following setting security.workspace.trust.enabled. Once enabled, you will see the following dialog when opening folders in VS Code.

Workspace Trust Startup Dialog

This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting security.workspace.trust.startupPrompt.

You can follow the development of Workspace Trust and provide feedback in issue #106488.

Workspace trust API

First off, all of what I am about to say can be found in issue #120251. That issue will include discussion of the feature and any updates to the feature.

The Workspace Trust extension API is now in stable. This allowed us to release the first cut of our guide for onboarding your extension to Workspace Trust. The API is small, so here is a quick look.

You can declare your extension to provide complete, partial or no support in untrusted workspaces using the untrustedWorkspaces capability in package.json.

The following example declares that the extension is supported completely in untrusted workspaces. In this case, the extension is enabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}

The next example declares that the extension is not supported in untrusted workspaces. In this case, the extension is disabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": false
  }
}

The third option is to declared limited support. There are three tools provided to you when you select the limited option.

First, if you have a setting that can be configured in the workspace but requires the workspace to be trusted in order to apply the workspace value, then you can include the setting using restrictedConfigurations array property in untrustedWorkspaces object. Doing so, VS Code will ignore the workspace value of these restricted settings when your extension reads these settings values using the VS Code Workspace Configuration API.

The following example declares the settings that are restricted in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": "limited",
    "restrictedConfigurations": [
      "markdown.styles"
    ]
  }
}

Next, you can also check and listen if the current workspace is trusted or not programmatically using the following API:

export namespace workspace {
  /**
   * When true, the user has explicitly trusted the contents of the workspace.
   */
  export const isTrusted: boolean;
  /**
   * Event that fires when the current workspace has been trusted.
   */
  export const onDidGrantWorkspaceTrust: Event<void>;
}

Lastly, you can hide commands or views declaratively with the isWorkspaceTrusted context key in your when clauses.

A far more detailed guide on how to onboard which will be updated as we receive feedback can be found in issue #120251.

Rollout plan

Workspace Trust will remain disabled for the month of May, but we are planning on enabling this by default in the future. To prepare for that day, we would love for you to try it out and provide feedback.

We'd love your feedback

Since this issue was created in an automated fashion, we won't be monitoring the responses in this issue (our notifications would explode!). Instead we ask you to drop questions, and feedback in issue #120251 as we've mentioned above.

We're excited to see what you do with workspace trust!

qlikview-vars terminates with exit code: 1

I've been trying for quite some time to get the qlikview-vars conversion to work, but it keeps terminating with exit code 1.
I've tried disabling powershell, but the error persists.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.