No consistency checks between access control signatures and page or action signatures
I am not sure this is checked in the compiler, however, it would provide a helpful addition when editing WebDSL applications:
I am currently allowed by the editor to write:
rule template A() {true}even though template A does not have to exist. I frequently run into the problem where I change my page’s signature, but forget to change the signature of the access control rule. A check for access control rules that do not match any templates, actions or pages would be nice.
Submitted by Sander Vermolen on 16 April 2010 at 13:08
Issue Log
On 16 April 2010 at 14:34 Nathan Bruning commented:
That would be nice. Note that the compiler (should) issue a warning if an access control rule does not match anything.
[ webdslc | info ] stage 5: access control Access control warning: unused rules: rule page thisPageDoesNotExists()
Getting this warning in the editor requires two major changes:
- moving the compiler warnings from desugaring (weaving) phase to typecheck phase
- multi-file typechecking support in Spoofax (reporting errors in a file other than the currently opened file)
On 9 June 2010 at 13:49 Lennart Kats closed this issue.
On 9 June 2010 at 13:49 YellowGrass commented:
Log in to post comments