Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
platform
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 157
    • Issues 157
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • simantics
  • platform
  • Issues
  • #619

Closed
Open
Opened Oct 07, 2020 by Tuukka Lehtonen@lehtonenOwner

Relative imports for SCL scripts

SCL scripts are currently executed so that CommandSession doesn't currently have any idea of where the executed script comes from in the database. It just gets it as a String.

Users would naturally like to import SCL modules in SCL scripts with relative paths but this is not possible as there is no context to resolve the relativity based on.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: simantics/platform#619