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

HPCC-28073 Additional service calls to be added to Dali Admin #17627

Merged
merged 1 commit into from
Aug 21, 2023

Conversation

kunalaswani
Copy link
Contributor

@kunalaswani kunalaswani commented Jul 31, 2023

Add and Delete functionality and some additional read functions added to Dali Admin UI.

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@github-actions
Copy link

@kunalaswani
Copy link
Contributor Author

@jeclrsg and @GordonSmith DaliImport and DaliCount seem to be giving me a bit of trouble, please review.

Copy link
Contributor

@jeclrsg jeclrsg left a comment

Choose a reason for hiding this comment

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

@kunalaswani Added a couple comments that I think might be related to the problems you were having w/ the Count and Import components. Also, the Ping one could be deleted I think.

esp/src/src-react/components/DaliCount.tsx Outdated Show resolved Hide resolved
esp/src/src-react/components/DaliPing.tsx Outdated Show resolved Hide resolved
esp/src/src-react/components/DaliImport.tsx Outdated Show resolved Hide resolved
@kunalaswani kunalaswani force-pushed the HPCC-28073 branch 2 times, most recently from 42b13a4 to 9dfaa23 Compare August 1, 2023 08:43
@kunalaswani
Copy link
Contributor Author

@jeclrsg DaliImport and DaliCount updated, waiting on @wangkx to determine removal of DaliPing.

@kunalaswani kunalaswani force-pushed the HPCC-28073 branch 2 times, most recently from 73e92a6 to 30b46c8 Compare August 2, 2023 08:32
message: nlsHPCC.DaliPromptConfirm,
onSubmit: React.useCallback(() => {
myDaliService.Import({ XML: xml, Path: path, Add: add }).then(response => {
const data = csvParse(response.Result);
Copy link
Member

Choose a reason for hiding this comment

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

I am curious why the csvParse() is used in DaliImport and DaliDelete and the parser.parse() is used for DaliAdd and DaliCount. In DaliCount, the response.Result is an integer. In DaliAdd/DaliDelete/DaliImport, the response.Result is a string.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For DaliCount using csvparse causes an error where WsDali.CountResponse.Result: number but WsDali.CountRequest.Path?: string... which is why we are using the parser.parse().

DaliAdd was switched back to csvParse, that was an error.

Copy link
Member

@wangkx wangkx left a comment

Choose a reason for hiding this comment

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

I did not spot any issue.

const [columns, setColumns] = React.useState<IColumn[]>([]);
const [items, setItems] = React.useState<any[]>([]);
const [path, setPath] = React.useState<string>("");
const [value, DaliAdd] = React.useState<string>("");
Copy link
Contributor

Choose a reason for hiding this comment

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

missed this earlier, but "DaliAdd" here should be "setValue"


const onSubmit = React.useCallback(() => {
myDaliService.Count({ Path: path }).then(response => {
const data = parser.parse(response.Result);
Copy link
Contributor

Choose a reason for hiding this comment

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

The import for parser doesn't seem to be correct. The only similar import I could find is import * as parser from "dojox/xml/parser"; (eg, https://github.com/hpcc-systems/HPCC-Platform/blob/master/esp/src/src/ESPGraph.ts#L4 and a few other places). But I don't think that's what you want either, since response.Result is a number, rather than something to be parsed, as you and Kevin were discussing.

I think you'd need to define data and columns as arrays containing one item. Maybe something like:

const data = [{
  key: "Result",
  result: response.Result
}];

const columns = [{
  key: "Result",
  name: "Result",
  fieldName: "result",
  minWidth: 100
}];

https://developer.microsoft.com/en-us/fluentui#/controls/web/detailslist

Add and Delete functionality and some additional read functions added
to Dali Admin UI.

Signed-off-by: Kunal Aswani <[email protected]>
@GordonSmith GordonSmith merged commit 0acd74d into hpcc-systems:candidate-9.2.x Aug 21, 2023
51 checks passed
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.

4 participants