Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

project/instance specifics: make sure evaluation order is always the same #507

Open
dariok opened this issue Apr 1, 2022 · 1 comment
Open

Comments

@dariok
Copy link
Owner

dariok commented Apr 1, 2022

  1. project specific function
  2. project specific HTML
  3. instance specific function
  4. instance specific HTML
  5. generic solution
dariok added a commit that referenced this issue May 5, 2022
project.xqm overrides instance.xqm
makes findProjectFunction() simpler
changes behaviour of getProjectFunction()

Cf. #510 #508 #507
@dariok
Copy link
Owner Author

dariok commented Aug 10, 2023

Perhaps have a generic function that works on the name only – hence, not only the eval order would be the same everywhere but also the names for functions and files.

However, this should wait till after the templating ( #532 ) has been overhauled.

dariok added a commit that referenced this issue Sep 18, 2023
These go through the templating system an can be up to 1s faster
than using an XQuery function in project.xqm

This will still need #507
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant