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

Let UI use maven generated YAML DSL sub schema #147

Closed
igarashitm opened this issue Sep 22, 2023 · 0 comments · Fixed by #148
Closed

Let UI use maven generated YAML DSL sub schema #147

igarashitm opened this issue Sep 22, 2023 · 0 comments · Fixed by #148
Assignees
Milestone

Comments

@igarashitm
Copy link
Contributor

Please describe the task that needs to be done

Following up #138 and #145, let ui use maven generated sub schema and remove ui generated sub schema in camel-schemas-processor.ts

@igarashitm igarashitm self-assigned this Sep 22, 2023
igarashitm added a commit to igarashitm/kaoto that referenced this issue Sep 22, 2023
Fixes: KaotoIO#147

ATM sub schemas are not used by UI. We'll soon use for Beans editor (#8) and will be easier to identify the sub schema by its name being same as the property name - for example, `beans` to be a name for the beans sub schema. The old verbose name were moved as `description` in the index.json.
We might want to generate an enum of these sub schema names and put in .d.ts.
igarashitm added a commit to igarashitm/kaoto that referenced this issue Sep 22, 2023
Fixes: KaotoIO#147

ATM sub schemas are not used by UI. We'll soon use for Beans editor (#8) and will be easier to identify the sub schema by its name being same as the property name - for example, `beans` to be a name for the beans sub schema. The old verbose name were moved as `description` in the index.json.
We might want to generate an enum of these sub schema names and put in .d.ts.
lordrip pushed a commit that referenced this issue Sep 23, 2023
Fixes: #147

ATM sub schemas are not used by UI. We'll soon use for Beans editor (#8) and will be easier to identify the sub schema by its name being same as the property name - for example, `beans` to be a name for the beans sub schema. The old verbose name were moved as `description` in the index.json.
We might want to generate an enum of these sub schema names and put in .d.ts.
@lhein lhein added this to the Feature Parity milestone Nov 2, 2023
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 a pull request may close this issue.

2 participants