Async methods?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the Editor validator API and the proposed ValidatorAsync usage in this issue. Determine which validation and callback paths would need asynchronous support, then define the expected API and completion criteria before implementation. No files or tests are identified in the issue.
Written by the indexing model from the issue text.
Description
For example Validate Async?
IE:
var editor = new Editor(db, "FieldDefinition", "Id")
.ValidatorAsync(async (editor, action, data) =>
{
// ...
var hasPermission = await policyServerRuntimeClient.HasPermissionAsync(this.User, "WriteInventory");
})
- Dominant language
- C#
- Stars
- 19
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DataTables/NET
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
DataTables/NET#27 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
DataTables/NET#24 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DataTables/NET#18 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
DataTables/NET#17 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
DataTables/NET#16 · 1 comment ·
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·