-
Notifications
You must be signed in to change notification settings - Fork 3
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
#245: Implemented support for Json for language definition #246
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
61d0d55
#245: Implemented support for Json for language definition
tomuben dea3e01
Added language_definitions.json
tomuben 73ddc43
Changed to list of aliases
tomuben 652dd9e
Apply suggestions from code review
tomuben 3f2345b
1. Added "schema_version"
tomuben 38c1c88
Added a check for the schema version
tomuben 3bc5760
Fixed import path of ValidationError
tomuben File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,7 +8,7 @@ t.b.d. | |
|
||
## Features | ||
|
||
n/a | ||
- #245: Implemented support for Json for language definition | ||
|
||
## Refactoring | ||
|
||
|
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
from dataclasses import dataclass | ||
from enum import Enum | ||
from pathlib import PurePosixPath | ||
from typing import List | ||
|
||
from pydantic import BaseModel | ||
|
||
|
||
class SLCLanguage(str, Enum): | ||
Java = "java" | ||
Python3 = "python" | ||
R = "r" | ||
|
||
|
||
class SLCParameter(BaseModel): | ||
""" | ||
Key value pair of a parameter passed to the Udf client. For example: `lang=java` | ||
""" | ||
|
||
key: str | ||
value: List[str] | ||
|
||
|
||
class UdfClientRelativePath(BaseModel): | ||
""" | ||
Path to the udf client relative to the Script Languages Container root path. | ||
For example `/exaudf/exaudfclient_py3` | ||
""" | ||
|
||
executable: PurePosixPath | ||
|
||
def __str__(self) -> str: | ||
return str(self.executable) |
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
from dataclasses import dataclass | ||
from typing import List | ||
|
||
from pydantic import BaseModel | ||
|
||
from exasol.slc.models.language_definition_common import ( | ||
SLCLanguage, | ||
SLCParameter, | ||
UdfClientRelativePath, | ||
) | ||
|
||
LANGUAGE_DEFINITON_SCHEMA_VERSION = 1 | ||
|
||
|
||
class LanguageDefinition(BaseModel): | ||
""" | ||
Contains information about a supported language and the respective path of the UDF client of an Script-Languages-Container. | ||
""" | ||
|
||
protocol: str | ||
aliases: List[str] | ||
language: SLCLanguage | ||
parameters: List[SLCParameter] | ||
udf_client_path: UdfClientRelativePath | ||
|
||
|
||
class LanguageDefinitionsModel(BaseModel): | ||
""" | ||
Contains information about all supported languages and the respective path of the UDF client of an Script-Languages-Container. | ||
""" | ||
|
||
schema_version: int | ||
|
||
language_definitions: List[LanguageDefinition] |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add environment variables, for example for the option parser
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, let's do it if we decided to really use it, because the alternative would be to use the
parameters
field