Ivy

Open
#505 15 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript

Research direction

Start by tracing the packaging and import relationships among the auth, manager, grid, and resource modules described in the issue. Confirm how Ivy detects and processes each module and where the lock-file conflict occurs. Done means the modules have a single entry point per module and no longer trigger the reported duplicate-processing error.

Written by the indexing model from the issue text.

Description

@travist I debugged the issue with Ivy today.
The auth, manager, grid, and resource modules are packed individually but contain references for each other, eg. manager imports auth. Ivy detects the modules as standalone packages and tries to manage async, but it reaches auth through manager as well, then throws an error since there is a lock file indicates it already processing it.
The solution would be re-structuring the lib to having only 1 entry point for each module for Ivy.

Dominant language
TypeScript
Stars
706
Forks
493
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from formio/angular

All issues in formio/angular

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.