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

Adds scheme names/labels section #153

Open
wants to merge 15 commits into
base: main
Choose a base branch
from
Open

Conversation

aarongundel
Copy link
Collaborator

Adds scheme names/labels section

@aarongundel aarongundel linked an issue Dec 13, 2024 that may be closed by this pull request
@aarongundel
Copy link
Collaborator Author

This will need to merge into main before/at the same time as JC's form editor ticket.

@aarongundel aarongundel marked this pull request as ready for review December 18, 2024 17:11
Copy link
Contributor

@chrabyrd chrabyrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works well, just some code design questions

Copy link
Contributor

@chrabyrd chrabyrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There appear to be some warnings in the console relating to various Scheme* components. Mind giving those a look?

But yeah overall looking good 👍

/>
<Column
field="appellative_status_ascribed_name_content"
header="Label"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i18n for headers 😄

@@ -26,7 +26,9 @@ function onUpdate(val: string[]) {
<div v-if="mode === EDIT">
<ResourceInstanceRelationshipsEditor
:options="options"
:val="value?.map((x) => x.resourceId) ?? []"
:val="
value?.map((referenceValue) => referenceValue.resourceId) ?? []
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️


async function deleteSectionValue(tileId: string) {
const result = await deleteSchemeLabelTile(tileId);
if (result) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, there should be error handling for sure. IMO wrap this in a try/catch that will raise a Toast error. I'd say same with getSectionValue and any other API.

@aarongundel aarongundel requested a review from chrabyrd December 24, 2024 00:04
@aarongundel
Copy link
Collaborator Author

There is a second, related item to genericize the label viewer. I separated it from this PR to get commentary on patterns therein. See #161 - set to merge into this PR.

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.

Scheme Labels Report sections
3 participants