ampersandtarski / ampersand-language-support Goto Github PK

Please support the ENFORCE statement.

When I run the debugger (F5-key) to debug langauge support, VSCode overwrites the language support for Ampersand that it normally uses with what we have in this repository, allowing me to debug stuff that is in the repo before it is deployed. Then, it tries to activate the 'new' extension.

When doing so, I get the following error:

@hanjoosten: can you fix this?

The following purpose statement is correct. However, the colour of the (optional) signature is red:

Syntax colouring of purpose statement lacks support for IDENT and VIEW

Something still red, while it is valid syntax:

@hanjoosten: some time ago I released yet another version of the langauge support. The result was that it nicely updated in VSCode, but if you look at the railroad tracks between the master and development branches, they do not show that this has been done. You noticed this already in earlier releases. This issue is to let you know this hasn't been resolved yet.

The MAINTAINS statement may refer to more than one rule, that is to be maintained by (also more than one) ROLEs. Currently, if more than one RULE is specified, the colour still turns red:

In this repo, we are putting information about the syntax of Ampersand. The ampersand compiler also carries this information . We want these two to be in sync. How can we make sure that this happens?

Challenge: When you miss the popup window you need to manually go to the correct adress.

Solution: The idea for this is to add a new way to open your portforwarded port adress from vscode. A few ideas currently are:

• An option in the menus
• An button
• Letting the popup stay open for longer
• Leave the popup open
• Opening the browser with the correct adress when command is run

Ik ben een beetje aan het prutsen met die propbutton en ik kwam een foutje tegen
Maar als je een propbutton aanmaakt, vult hij automatisch aan

                   BOX<PROPBUTTON>
                   [ property: propertyrelation cRUd
                     disabled: expression cRud
                     hide: expression cRud
                   ]

Waarna de compiler een fout geeft omdat de komma’s missen.

We should stop a running prototype before we start a new one to make sure the new prototype can start on the default forwarded port

The name of a PATTERN is red, it shouldn't be:

Syntax as described in AmpersandTarski/Ampersand#851 is not supported

CLASSIFY A IS B

Make the codespace run minikube.

According to the documentation of BOX <TABLE, I should be able to write BOX <TABLE hideNoRecords> in an INTERFACE, e.g.

INTERFACE "Login" FOR Anonymous: sessionIsAnon cRud BOX <RAW>
   [ "Login bar": I-sessionAccRegForm;sessionAccRegForm~ cRud BOX <TABLE hideNoRecords>
      [ "Userid": loginUserid cRUd
      , "Password": loginPassword cRUd -- crUd is needed for Passwords
      , "IdP": loginIdP cRUd
      , "Login": I cRud BOX <PROPBUTTON> 
         [ "property": sessionLoginReq cRUd
         , "disabled": I - (loginUserid;loginUserid~ /\ loginPassword;loginPassword~) cRud
         ]
  ]

However, this produces an error:

We expect the release of Ampersand 4.0 in the near future. This totally breaks the command line interface. The VScode plugin should be modified in a way that it looks for the version of Ampersand, then gives the right command to start the daemon. The command has changed from ampersand --daemon to ampersand daemon. Not a big deal, but I have to find out how this should be done (my Typescript is even lousier than my Haskell knowledge)

For a lot of statements, there is syntactic help. I would expect that if I start typing the keyword RULE, I would get a template for that statement as well. It is missing.

Worklist for fixing in the syntax coloring stuff:

• fileids in INCLUDE statements should be colored as they are in comments.
• last ] in a POPULATION statement is not colored correctly
• HTML TEMPLATEs are not recognized (and consequently they are colored as illegal text)

I am trying to be able to publish this extention in the VS Code repo, so users can have a great experience to obtain it in a proper way.

I have followed the instructions from the documentation, but then when I press F5 to test it, I get an error message Activating extension 'ampersandtarski.language-ampersand' failed:

I tried all kinds of things, but until now without luck.

Any help is very much appreciated!

Als je de snippet

POPULATION "Relname" CONTAINS [ ("", "") ]

gebruikt, geeft de compiler een fout omdat om Relname geen "" hoeven te staan.

POPULATION Relname CONTAINS [ ("", "")]

My vscode has been updated to run Ampersand (ADL) language support 0.2.9.
I have complied with the requirement that the ampersand.exe is in the path: I have opened a command terminal, typed ampersand --version, and got the reply

14:18:41 C:\Ampersand\Git\ssif\_CZ> ampersand --version
SET AMPvsnr=Ampersand-v3.11.1 [development:e7be402f9], build time: 05-Aug-18 18:52:56 W. Europe Daylight Time

When I press Ctrl-Shift-B, and attempt to run the ampersand task, the output window contains

Error: The npm task detection didn't contribute a task for the following configuration:
{
    "type": "npm",
    "script": "compile",
    "path": "ampersandtarski.language-ampersand-0.2.8/",
    "problemMatcher": []
}
The task will be ignored.
Error: The npm task detection didn't contribute a task for the following configuration:
{
    "type": "npm",
    "script": "compile",
    "path": "ampersandtarski.language-ampersand-0.2.8/",
    "problemMatcher": []
}
The task will be ignored.

Note that in the path, it talks about version 0.2.8.
Perhaps the task should explicitly be identified as one of the contributions of the language extension?
And perhaps the path should refer to version 0.2.9?

Due to Ampersand PR 871 which fixes Issue 616, the keyword OBJECT will be introduced and added to the possibilities of the types in REPRESENT <concept> TYPE <types>.

This issue requests adding this to the VSCode language support extension.

Warning die gegeven word bij het bouwen is deze:

This extension consists of 2558 files, out of which 1371 are JavaScript files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension . You should also exclude unnecessary files by adding them to your .vscodeignore: https://aka.ms/vscode-vscodeignore

spaces between the target concept and the closing bracket of a signature, now colours red, while ampersand itself accepts this:

I would expect the REF part not to be coloured red:

Please prepare for AmpersandTarski/Ampersand#1087

BOX attributes are introduced as described in AmpersandTarski/Ampersand#1084

@Michiel-s coined the idea of having a switch in Ampersand that would allow a single file to be tested just for syntax errors, and make the resulting errors (if any) importable by VSCode. This would enable VSCode to test the syntax of texts that you edit dynamically, similar to what it does to standard languages/grammars.

Of course, this would also need to be included in the Ampersand language support...

If one wants to know the currently available version of Ampersand, one can use the command in vscode for it:

However, this is broken:

The following statement is marked red, but it is valid syntax:
POPULATION r[A*B] CONTAINS [("a1","b1")]

Furthermore, if you place double quotes around the relationsignature "r[A*B]", the syntax coloring indicates that this is accepted, but the compiler doesn't allow for this.

See the red parts in the following script. I would expect these expressions not to be red, for they are valid

(example taken from issue AmpersandTarski/Ampersand#517 )

Refactor current terminal utils to use Then consistently and also create a class for input instead of variable parameters

The META statement allows flexible definition of key-value pairs. (mostly for use with documentation generation).

META String String

I have solved AmpersandTarski/Ampersand#925, which is about the deprication of <ROWSNH>.

For some reason, this template is special in the syntax colouring. That should not be (any longer).