fix: remove duplicated mock definitions causing warnings and operational failures #10927
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.
The current code will give warnings after
npm start
is initiated:The reason is that
listTableList.ts
andrequestRecord.mock.js
have the same mock interface definitions.Moreover, because
requestRecord.mock.js
will overwrite the mock definitions inlistTableList.ts
, the addition, modification, and deletion operations on the data in the query list pagesrc\pages\TableList\index.tsx
will have no effect, because it will always follow the hardcoded data inrequestRecord.mock.js
.This
requestRecord.mock.js
seems to be a temporary file used for generating type definitionssrc/types/index.d.ts
. Since the type definitions have already been generated, it seems that it is no longer needed. Can it be deleted? If so, the warning will disappear, and the operations on the query list page will also respond normally.