Document setup for export service#241
Merged
ArtyomSavchenko merged 2 commits intohcengineering:mainfrom Dec 13, 2025
Merged
Conversation
Signed-off-by: Antonio Cheong <acheong@duti.dev>
|
Connected to Huly®: SELFH-240 |
ArtyomSavchenko
approved these changes
Dec 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #175 where when you export with the default setup, it throws an error:
To be decided: Should export service be built in or optional? My opinion is that it should be built in since the functionality shows on the front-end by default. PR has it as optional because it's not my decision to make.