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

Fix #176, Fix #272: Fix references and update in wfconfig files #275

Merged
merged 1 commit into from
May 26, 2020

Conversation

martin-fleck-at
Copy link
Contributor

Server:

  • Quote references to allow spaces in names
    -- Adapt Xtext grammar to use String instead of FQN
    -- Ensure proposal provider offers quoted strings
    -- Adapt examples with quoted strings

Client:

  • Notify wfconfig server on *.coffee changes to correctly update index

Signed-off-by: Martin Fleck [email protected]

Server:
- Quote references to allow spaces in names
-- Adapt Xtext grammar to use String instead of FQN
-- Ensure proposal provider offers quoted strings
-- Adapt examples with quoted strings

Client:
- Notify wfconfig server on *.coffee changes to correctly update index

Signed-off-by: Martin Fleck <[email protected]>
@martin-fleck-at martin-fleck-at requested a review from eneufeld May 14, 2020 11:00
@eneufeld
Copy link
Contributor

@martin-fleck-at looks good
Can we force a refresh of the wfconfig editor?
See this behavior:
CoffeeEditorWfConfigRefresh

If it is complicated I suggest to create a follow up

@martin-fleck-at
Copy link
Contributor Author

@eneufeld Just from memory: The "references" in the wfconfig file are not real cross references but rather validated strings. As such the language server does not trigger a re-validation of the wfconfig file because it doesn't know that the string it has comes from the changed .coffee file.

I believe we could trigger a build/validation ourselves. However, since that information is not stored by Xtext we would need to track that reference information ourselves. Alternatively we would need to build/validate all wfconfig files if there is a change in a .coffee file just in case one of the files references content from that file. I believe the validation of those files is fast and the files are typically not that large. Still, it wouldn't be the most elegant solution.

In any case, I believe it makes sense to track that in a separate task for now as we have the following options: real cross references, string references but tracked reference information, build/validation of all wfconfig files.

@eneufeld
Copy link
Contributor

Thank you for the reply. I will create a follow up.

@eneufeld eneufeld merged commit 4372c98 into master May 26, 2020
@eneufeld eneufeld deleted the issues-176-272 branch May 26, 2020 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants